| 3 | Approval of the Agenda | |
|---|---|---|
| R3-203000 | RAN3#108-e Meeting Agenda | Chairman (Ericsson) |
| 4 | Approval of the minutes from previous meetings | |
| R3-203001 | RAN3#107Bis-e Meeting report | ETSI - MCC |
| 5 | Documents for immediate consideration | |
| R3-203543 | List of E-mail Discussions | RAN3 Chairman |
| R3-203544 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-204023 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| 8.1 | New Incoming LSs | |
| R3-203105 | LS on updated Rel-16 LTE and NR parameter lists | 3GPP RAN1 |
| R3-203106 | Reply LS on manual CAG selection | 3GPP RAN2 |
| R3-203108 | LS on UAC applicability to IABs | 3GPP RAN2 |
| R3-203110 | LS on updated Inactive AS context | 3GPP RAN2 |
| R3-203111 | Response LS on the “LS OUT on Location of UEs and associated key issues” | 3GPP RAN2 |
| R3-203112 | LS on Support of inter-RAT HO for fast MCG recovery | 3GPP RAN2 |
| R3-203113 | LS on IAB supporting in NPN deployment | 3GPP RAN2 |
| R3-203114 | Response LS on the support for ECN in 5GS | 3GPP RAN2 |
| R3-203116 | LS on report mapping for UE positioning measurement | 3GPP RAN4 |
| R3-203118 | Reply LS on Local NR positioning in NG-RAN | 3GPP SA2 |
| R3-203119 | Reply LS on QoS Monitoring for URLLC | 3GPP SA2 |
| R3-203121 | LS on SA WG2 status of MT-EDT in Rel-16 | 3GPP SA2 |
| R3-203123 | Reply LS to LS on EN-DC related MDT configuration details | 3GPP SA5 |
| R3-203124 | LS on Reply on QoE Measurement Collection | 3GPP SA5 |
| R3-203125 | LS on Reply on QoE Measurement Collection | 3GPP SA5 |
| R3-203137 | Discussion on updated Inactive AS context | China Telecom,ZTE,CATT |
| R3-203138 | Draft Reply LS on updated Inactive AS context | China Telecom, ZTE |
| R3-203142 | Issue on Storing Inactive AS Context in SCG | LG Electronics |
| R3-203143 | Correction for TS38.473 on storing inactive AS context in SCG | LG Electronics |
| R3-203158 | Discussion on support of inter-RAT HO for fast MCG recovery | ZTE |
| R3-203159 | CR36423 for support of inter-RAT HO for fast MCG recovery | ZTE |
| R3-203160 | CR38423 for support of inter-RAT HO for fast MCG recovery | ZTE |
| R3-203161 | [Draft] Reply LS on Support of inter-RAT HO for fast MCG recovery | ZTE |
| R3-203287 | Support of inter-RAT handover in response to MCGFailureInformation | Nokia, Nokia Shanghai Bell, Huawei |
| R3-203320 | Updates for QoE measurement support (X2AP, S1AP, RANAP) | Ericsson |
| R3-203321 | [Draft] LS on Reply on QoE Measurement Collection | Ericsson |
| R3-203322 | CR TS 25.413 on QoE measurement collection support for RANAP | Ericsson |
| R3-203323 | CR TS 36.413 on QoE measurement collection support for S1AP | Ericsson |
| R3-203324 | CR TS 36.423 on QoE measurement collection support for X2AP | Ericsson |
| R3-203366 | Discussion on PWS Concurrent Warning Message Indication usage | Ericsson |
| R3-203367 | Clarifications on Concurrent Warning Message broadcast | Ericsson |
| R3-203368 | Clarifications on Concurrent Warning Message broadcast | Ericsson |
| R3-203369 | Discussion on Inactive UE Context stored at gNB-DU | Ericsson |
| R3-203370 | Corrections of Inactive UE Context stored at gNB-DU | Ericsson |
| R3-203371 | Support of inter-RAT HO for fast MCG recovery | Ericsson |
| R3-203372 | Support of inter-RAT HO for fast MCG recovery in Xn AP | Ericsson |
| R3-203373 | Support of inter-RAT HO for fast MCG recovery in X2 AP | Ericsson |
| R3-203485 | Discussion on Qos monitoring for URLLC | Huawei |
| R3-203486 | Qos monitoring for URLLC | Huawei |
| R3-203487 | Qos monitoring for URLLC | Huawei |
| R3-203488 | Qos monitoring for URLLC | Huawei |
| R3-203489 | Qos monitoring for URLLC | Huawei |
| R3-203490 | Qos monitoring for URLLC | Huawei |
| R3-203519 | CR38473 to update inactive AS context | ZTE, China Telecom, CATT |
| R3-203551 | Inter-RAT HO support for fast MCG recovery | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203552 | Inter-RAT HO support for fast MCG recovery | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203553 | [DRAFT] Reply LS on Support of inter-RAT HO for fast MCG recovery | Huawei |
| R3-203554 | Update the UE Inactive AS context | Huawei |
| R3-203555 | [DRAFT]Reply LS on updated Inactive AS context | Huawei |
| R3-203556 | Discussion on QoE measurement collection | Huawei |
| R3-203584 | Discussion on updated Inactive AS context | NEC |
| R3-203585 | On updated Inactive AS context | NEC |
| R3-203837 | IAB support in NPN | Huawei |
| R3-203838 | Draft Reply LS on IAB supporting in NPN deployment | Huawei |
| R3-203846 | Clarifications on concurrent broadcasting of CMAS | Samsung |
| R3-203847 | CR on Concurrent Warning Message Indicator over F1 (Rel-15) | Samsung |
| R3-203848 | CR on Concurrent Warning Message Indicator over F1 (Rel-16) | Samsung, Ericsson |
| R3-203868 | On QoE Measurement Collection | ZTE |
| R3-203869 | QoE Measurement Collection Rel-15 | ZTE |
| R3-203870 | QoE Measurement Collection Rel-16 | ZTE |
| R3-203898 | (TP for TS 38.423) Support inter-RAT HO fast MCG recovery | Qualcomm Incorporated |
| R3-203908 | (TP for TS 36.423) Support of inter-RAT HO for fast MCG recovery | Qualcomm Incorporated |
| R3-203936 | Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | 3GPP CT1 |
| R3-203937 | LS on Concurrent Broadcasting for CMAS | 3GPP CT1 |
| R3-203938 | LS reply to RAN WG3 LS on AS rekeying handling | 3GPP SA3 |
| R3-203939 | LS on 5GC assisted cell selection for accessing network slice | 3GPP SA1 |
| R3-203940 | Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | 3GPP SA1 |
| R3-203941 | reply LS on UAC applicability to IABs | 3GPP SA1 |
| R3-203942 | Reply LS on manual CAG selection | 3GPP SA1 |
| R3-203943 | reply LS on GSMA NG.116 Attribute Area of service and impact on PLMN | 3GPP SA1 |
| R3-204027 | Corrections of Inactive UE Context stored at gNB-DU | Ericsson |
| R3-204028 | CB: # 72_UpdatedInactiveASctxt - Summary of offline discussion | Ericsson - moderator |
| R3-204029 | Support of inter-RAT handover in response to MCGFailureInformation | Nokia, Nokia Shanghai Bell, Huawei |
| R3-204030 | Inter-RAT HO support for fast MCG recovery | Huawei, Nokia, Nokia Shanghai Bell |
| R3-204031 | Inter-RAT HO support for fast MCG recovery | Huawei, Nokia, Nokia Shanghai Bell |
| R3-204032 | [DRAFT] Reply LS on Support of inter-RAT HO for fast MCG recovery | Huawei |
| R3-204033 | CB: # 73_IRAT_HOforFastMCGrecovery - Summary of offline discussion | Nokia - moderator |
| R3-204034 | Qos monitoring for URLLC-Summary of offline disscussion | Huawei - moderator |
| R3-204035 | CB #75_QoEmeasCall - Summary of offline discussion | Ericsson - moderator |
| R3-204036 | CB #76_PWSconcurrent_broadcast-Summary of offline discussion | Samsung - Moderator |
| R3-204037 | CR on Concurrent Warning Message Indicator over F1 (Rel-15) | Samsung, Ericsson |
| R3-204038 | CR on Concurrent Warning Message Indicator over F1 (Rel-16) | Samsung, Ericsson |
| R3-204074 | CR TS 25.413 on QoE measurement collection support for RANAP | Ericsson |
| R3-204117 | CR TS 36.413 on QoE measurement collection support for S1AP | Ericsson |
| R3-204118 | CR TS 36.423 on QoE measurement collection support for X2AP | Ericsson |
| R3-204119 | CR TS 25.413 on QoE measurement collection support for RANAP | Ericsson |
| R3-204135 | Qos monitoring for URLLC | Huawei |
| R3-204136 | Qos monitoring for URLLC | Huawei |
| R3-204338 | Corrections of Inactive UE Context stored at gNB-DU | Ericsson, NEC |
| 8.2 | LSin received during the meeting | |
| R3-204107 | Reply LS on assistance indication for WUS | 3GPP RAN2 |
| R3-204108 | Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | 3GPP SA2 |
| R3-204109 | LS Reply on QoE Measurement Collection | 3GPP SA4 |
| R3-204125 | Reply LS on MDT and SON decisions related to RAN3 LSs | 3GPP RAN2 |
| R3-204126 | Reply LS on NAS Non delivery for RRC Inactive state | 3GPP SA2 |
| R3-204234 | Reply LS on updated Rel-16 LTE and NR parameter lists | 3GPP RAN2 |
| R3-204235 | Reply LS on cell specific signal/channel configurations | 3GPP RAN1 |
| R3-204236 | Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | 3GPP SA2 |
| R3-204237 | Reply LS on Stage 3 for V2X QoS | 3GPP SA2 |
| R3-204238 | Reply LS on early UE capability retrieval for eMTC | 3GPP SA2 |
| R3-204239 | Reply LS on NAS Non delivery for RRC Inactive state | 3GPP SA2 |
| R3-204240 | Reply LS on IAB supporting in NPN deployment | 3GPP SA2 |
| R3-204241 | Reply LS on S1/NG DAPS handover | 3GPP RAN2 |
| R3-204288 | Reply LS on energy efficiency | 3GPP SA5 |
| R3-204289 | Reply LS to LS on removal of Management Based MDT Allowed IE for NR | 3GPP SA5 |
| R3-204318 | LS on M.resm-AI “Requirements for energy saving management of 5G RAN system with AI | ITU-T SG2 |
| 8.3 | Left over LSs / pending actions | |
| R3-203126 | CR to TS36.423 on Correction of R3-202726 Agreed for EN-DC CSI-RS Transfer | China Telecom, ZTE, Huawei,CATT, Ericsson |
| R3-203812 | On stage 2 documentation of CSI-RS based handover | Nokia, Nokia Shanghai Bell |
| R3-204039 | CR to TS36.423 on Correction of R3-202726 Agreed for EN-DC CSI-RS Transfer | China Telecom, ZTE, Huawei, CATT, Ericsson |
| R3-204040 | TS38.300 Introduction of Inter-(en)gNB CSI-RS Based Mobility | Nokia |
| R3-204041 | CB: # 77_CSI-RS_st2_check-Summary of offlline discussion | Nokia - moderator |
| 8.3.1 | NR SCG Release for Power Saving | |
| R3-203109 | LS on NR SCG release for power saving | 3GPP RAN2 |
| R3-203162 | Discussion on NR SCG release for power saving | ZTE |
| R3-203163 | CR36423 for NR SCG release for power saving | ZTE |
| R3-203164 | CR38423 for NR SCG release for power saving | ZTE |
| R3-203165 | [Draft] Reply LS on NR SCG release for power saving | ZTE |
| R3-203223 | Correction of connected en-gNB Identifier | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203224 | Correction of connected en-gNB Identifier | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203284 | New Cause for release due to power saving in the UE | Nokia, Nokia Shanghai Bell |
| R3-203285 | New Cause for release due to power saving in the UE | Nokia, Nokia Shanghai Bell |
| R3-203286 | Response LS on NR SCG release for power saving | Nokia, Nokia Shanghai Bell |
| R3-203363 | On Rel-16 UE Power Saving | Ericsson |
| R3-203364 | Support of NR SCG release for power saving | Ericsson |
| R3-203365 | Support of NR SCG release for power saving | Ericsson |
| R3-203482 | Discussion on NR SCG release for power saving | CATT |
| R3-203483 | Introducing UAI to RRC transfer | CATT |
| R3-203586 | Discussion on cause value for SN release for power saving | NEC |
| R3-203587 | Cause value for SN release for power saving | NEC |
| R3-203860 | Introducing UAI to RRC transfer | CATT |
| R3-204042 | CB: # 78 NR_SCGrelease_PwrSaving-Summary of offline discussion | Nokia - moderator |
| 9.2.1 | Rel-15 WUS | |
| R3-203117 | Reply LS on assistance indication for WUS | 3GPP SA2 |
| R3-203182 | Consideration on WUS awareness | ZTE, Ericsson |
| R3-203183 | [Draft] Reply LS on WUS | ZTE, Ericsson |
| R3-203184 | CR 36.300 for WUS awareness-r15 | ZTE, Ericsson |
| R3-203185 | CR 36.300 for WUS awareness | ZTE, Ericsson |
| R3-203211 | Consideration on Rel-15 WUS | Huawei |
| R3-203212 | Support of WUS | Huawei |
| R3-203213 | Support of WUS | Huawei |
| R3-203227 | [Draft]Reply LS on assistance indication for WUS | Huawei |
| R3-203348 | WUS Assistance Indication | Qualcomm Incorporated |
| R3-203349 | [DRAFT] Reply LS on assistance indication for WUS | Qualcomm Incorporated |
| R3-203435 | Correction of WUS Paging | Nokia, Nokia Shanghai Bell |
| R3-203436 | Correction of WUS Paging | Nokia, Nokia Shanghai Bell |
| R3-203437 | Correction of WUS Paging | Nokia, Nokia Shanghai Bell |
| R3-203438 | Response LS on Assistance Indication for WUS | Nokia, Nokia Shanghai Bell |
| R3-204043 | CB: # 79_Rel-15_WUS-Summary of offline discussion | ZTE - moderator |
| R3-204173 | CR 36.300 for WUS awareness-r15 | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Huawei |
| R3-204174 | CR 36.300 for WUS awareness | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Huawei |
| R3-204175 | Reply LS on assistance indication for WUS | Qualcomm Incorporated |
| R3-204303 | CR 36.300 for WUS awareness | ZTE, Ericsson |
| 9.2.2 | Others | |
| R3-203192 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| R3-203193 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| R3-204044 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| R3-204045 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| 9.3.1 | RAN Sharing | |
| R3-203245 | Clarification on network sharing scenario | ZTE Corporation |
| R3-203246 | Clarification on network sharing scenario | ZTE Corporation |
| R3-203293 | Correction for Network Sharing | Ericsson |
| R3-203294 | Correction for Network Sharing | Ericsson |
| R3-203374 | Correction of the connected en-gNBs | Ericsson |
| R3-203375 | Correction of the connected en-gNBs | Ericsson |
| R3-203376 | Finalisation of discussions on RAN sharing | Ericsson |
| R3-203545 | Correction of connected en-gNBs | Nokia, Nokia Shanghai Bell, Huawei |
| R3-203546 | Correction of connected en-gNBs | Nokia, Nokia Shanghai Bell, Huawei |
| R3-203809 | On the link between Global gNB ID and NCGI | Nokia, Nokia Shanghai Bell |
| R3-203810 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-203811 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-203934 | Response to R3-203809 | China Unicom |
| R3-203935 | Response to R3-203811 | China Unicom |
| R3-204046 | CB: # 80_RAN_sharing_main_disc-Summary of offline discussion | Ericsson - moderator |
| R3-204159 | Correction for Network Sharing | Ericsson |
| R3-204160 | Correction for Network Sharing | Ericsson |
| 9.3.2 | PWS Cancel | |
| R3-203259 | Further Discussion on PWS Cancel | ZTE Corporation |
| R3-203260 | Correction on PWS Cancel | ZTE Corporation |
| R3-203261 | Correction on PWS Cancel | ZTE Corporation |
| R3-203306 | PWS Cancel | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-203308 | Correction to the Notification Information IE in PWS CANCEL REQUEST message | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-203310 | Correction to the Notification Information IE in PWS CANCEL REQUEST message | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-203606 | Correction to PWS Cancellation | Samsung, LGU+ |
| R3-203607 | CR on PWS Cancellation corrections over F1 (Rel-15) | Samsung, LGU+ |
| R3-203608 | CR on PWS Cancellation corrections over F1 (Rel-16) | Samsung, LGU+ |
| R3-204050 | CB: #81_PWScancel-Summary of offline discussion | Nokia - moderator |
| R3-204089 | Section renumbering for PWS cancel | Huawei |
| R3-204090 | Section renumbering for PWS cancel | Huawei |
| R3-204315 | Addition of abnormal conditions in PWS Cancel procedure | Nokia, Nokia Shanghai Bell |
| R3-204316 | Addition of abnormal conditions in PWS Cancel procedure | Nokia, Nokia Shanghai Bell |
| R3-204321 | CB: #81_PWScancel-Summary of offline discussion | Nokia - moderator |
| 9.3.3 | DC Operation Mode | |
| R3-203295 | PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203296 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203297 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203298 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203299 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203300 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203301 | Support of PSCell/SCell-only operation mode | Ericsson, Nokia, Nokia Shangai Bell |
| R3-203439 | Support of PSCell/SCell-only Operation Mode over E1 | Nokia, Nokia Shanghai Bell |
| R3-203440 | Support of PSCell/SCell-only Operation Mode over E1 | Nokia, Nokia Shanghai Bell |
| R3-203441 | Support of PSCell/SCell-only Operation Mode over E1 | Nokia, Nokia Shanghai Bell |
| R3-203689 | Discussion on NSA mode indication over XnAP | CATT,China Telecom,ZTE |
| R3-203690 | Correction on NSA mode indication | CATT,China Telecom,ZTE |
| R3-203691 | Correction on NSA mode indication (Rel-16) | CATT,China Telecom,ZTE |
| R3-203692 | Correction on NSA mode indication | CATT,China Telecom,ZTE |
| R3-203693 | Correction on NSA mode indication (Rel-16) | CATT,China Telecom,ZTE |
| R3-203849 | Futher discussion on PScell/Scell only operation | Huawei |
| R3-203850 | Clarification to 38.473 on TAC presence in Serving Cell Info over F1 | Huawei |
| R3-203851 | Clarification to 38.473 on TAC presence in Serving Cell Info over F1 | Huawei |
| R3-203932 | Response to R3-203295 | CATT |
| R3-203933 | Response to R3-203295 | CATT |
| R3-204051 | CB: #82_Dcoperation_mode - Summary of offline discussion | Ericsson - moderator |
| 9.3.4 | Selected PLMN ID in INITIAL UE MESSAGE for Untrusted Non-3GPP Access | |
| R3-203207 | Consideration on Selected PLMN ID for untrusted non-3GPP access | Huawei |
| R3-203208 | Selected PLMN ID for untrusted non-3GPP access | Huawei |
| R3-203209 | Selected PLMN ID for untrusted non-3GPP access | Huawei |
| R3-203210 | Selected PLMN ID for untrusted non-3GPP access | Huawei |
| R3-203302 | Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-203303 | Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-204052 | CB: #83_SelPLMNID_non-3GPPaccess - Summary of offline discussion | Huawei - moderator |
| R3-204166 | Selected PLMN ID for untrusted non-3GPP access | Huawei |
| R3-204167 | Selected PLMN ID for untrusted non-3GPP access | Huawei |
| 9.3.5 | RRC Reconfiguration in DU-Initiated UE Context Modification Required | |
| R3-203255 | Discussion on the RRC Connection Reconfiguration Complete Indicator IE in SA case | ZTE Corporation |
| R3-203256 | Correction on RRC Connection Reconfiguration Complete Indicator | ZTE Corporation |
| R3-203258 | Correction on RRC Connection Reconfiguration Complete Indicator | ZTE Corporation |
| R3-203292 | RRC Reconfiguration in DU initiated UE Context Modification Required CR 38.473 | Ericsson |
| R3-203304 | RRC Reconfiguration in DU initiated UE Context Modification Required CR 38.473 | Ericsson |
| R3-203305 | RRC Reconfiguration in DU initiated UE Context Modification Required | Ericsson |
| R3-203609 | Clarification on RRC Reconfiguration Complete Indicator | Samsung |
| R3-203610 | Clarification on RRC Reconfiguration Complete Indicator (Rel-15) | Samsung |
| R3-203611 | Clarification on RRC Reconfiguration Complete Indicator (Rel-16) | Samsung |
| R3-203686 | Discussion on RRC Reconfiguration Complete Indicator from gNB-CU to gNB-DU | CATT |
| R3-203687 | Introduction of UE Reconfiguration Completion procedure | CATT |
| R3-203688 | Introduction of UE Reconfiguration Completion procedure(Rel-16) | CATT |
| R3-203834 | Clarification on interactions in gNB-DU initiated UE Context Modification procedure | Nokia, Nokia Shanghai Bell |
| R3-203835 | Clarification on interactions in gNB-DU initiated UE Context Modification procedure | Nokia, Nokia Shanghai Bell |
| R3-204053 | CB: #84_RRCreconfig_in_DU-initiated_UEctxtModRequired - Summary of offline discussion | ZTE - moderator |
| R3-204177 | Correction on RRC Connection Reconfiguration Complete Indicator | ZTE, Ericsson, Samsung |
| R3-204178 | Correction on RRC Connection Reconfiguration Complete Indicator | ZTE, Ericsson, Samsung |
| 9.3.8.1 | Other Corrections | |
| R3-203128 | Further Discussion on the semantics description of 5GS TAC and Served PLMNs | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-203130 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-203133 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-203134 | Discussion on PDCP Status Report indication over E1 | China Telecom Corporation Ltd. |
| R3-203135 | CR to 38.463 on introducing a PDCP Status Report indication in PDCP-Configuration | China Telecom Corporation Ltd. |
| R3-203136 | CR to 38.463 on introducing a PDCP Status Report indication in PDCP-Configuration | China Telecom Corporation Ltd. |
| R3-203139 | CR to38.422 on SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-203140 | CR to 38.462 on SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-203141 | CR to38.422 on SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-203189 | Correction for UL UP TNL Information | Nokia, Nokia Shanghai Bell, ZTE, China Telecom, Samsung |
| R3-203190 | Correction for UL UP TNL Information | Nokia, Nokia Shanghai Bell, ZTE, China Telecom, Samsung |
| R3-203203 | Correction on RRC Container in Initial UL RRC Messag Transfer | Huawei, China Telecom, CMCC |
| R3-203204 | Correction on RRC Container in Initial UL RRC Messag Transfer | Huawei, China Telecom, CMCC |
| R3-203250 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-203251 | TS38.423 Resolving Erroneous unknown-old-en-gNB-UE-X2AP-ID Rel-15 | ZTE |
| R3-203252 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-203253 | Add failure cause on Cell Deactivation | ZTE,China Telecom,China Unicom,CMCC |
| R3-203254 | Add failure cause on Cell Deactivation | ZTE,China Telecom,China Unicom,CMCC |
| R3-203257 | TS38.423 Resolving Erroneous unknown-old-en-gNB-UE-X2AP-ID Rel-16 | ZTE |
| R3-203377 | Cell Creation Rejection when max number of supported cells is exceeded at CU | Ericsson |
| R3-203378 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson |
| R3-203379 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson |
| R3-203380 | Overlapping bands handling | Ericsson |
| R3-203381 | Overlapping band handling CR 38.473 | Ericsson |
| R3-203382 | Overlapping band handling CR 38.473 | Ericsson |
| R3-203383 | Measurement gap deactivation over F1AP | Ericsson |
| R3-203384 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson |
| R3-203385 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson |
| R3-203386 | Correstion on PDU Session Resrouce Modification Procedures | Ericsson |
| R3-203387 | Correstion on PDU Session Resrouce Modification Procedures | Ericsson |
| R3-203442 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-203443 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-203444 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-203445 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-203472 | CR to 38.401 on SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-203476 | CR to 38.401 on SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-203478 | CR to 38.412 on RAN CONFIGURATION UPDATE on UE associated TNL | ZTE, China Telecom |
| R3-203479 | CR to 38.412 on RAN CONFIGURATION UPDATE on UE associated TNL | China Telecom, ZTE |
| R3-203481 | TS38.413 Reformulation of 8.3.4.4 Abnormal Conditions Rel-15 | ZTE |
| R3-203484 | TS38.413 Reformulation of 8.3.4.4 Abnormal Conditions Rel-16 | ZTE |
| R3-203491 | Correction to engNB's Configured TAC in S1 SETUP | Huawei |
| R3-203492 | Correction to engNB's Configured TAC in S1 SETUP | Huawei |
| R3-203493 | Correction to engNB's Configured TAC in S1 SETUP | Huawei |
| R3-203526 | Correction of NAS Non Delivery Indication | CATT |
| R3-203527 | Draft CR for 38.300 Correction on NAS NON Delivery | CATT |
| R3-203528 | Correction to NAS Non Delivery Indication | CATT |
| R3-203641 | Further discussion on NAS Non-Delivery | Huawei |
| R3-203642 | Further discussion on NAS Non-Delivery | Huawei |
| R3-203643 | Correction of Security Result | Huawei |
| R3-203644 | Correction of Security Result | Huawei |
| R3-203694 | Correction on RF parameters in NR cell information(X2AP) | CATT |
| R3-203695 | Correction on RF parameters in NR cell information(XnAP) | CATT |
| R3-203696 | Correction on RF parameters in NR cell information(F1AP) | CATT |
| R3-203700 | Location Report when AMF request report UE presence in the area of interest | Nokia, Nokia Shanghai Bell |
| R3-203701 | Location Report when AMF request report UE presence in the area of interest | Nokia, Nokia Shanghai Bell |
| R3-203823 | Correction for Handover Preparation Information | Nokia, Nokia Shanghai Bell |
| R3-203824 | Correction for Handover Preparation Information | Nokia, Nokia Shanghai Bell |
| R3-203825 | Correction for NR-DC bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-203826 | Correction for NR-DC bearer establishment | Nokia, Nokia Shanghai Bell |
| R3-203827 | Correction for Supported Slices on E1 | Nokia, Nokia Shanghai Bell |
| R3-203828 | Correction for Supported Slices on E1 | Nokia, Nokia Shanghai Bell |
| R3-203829 | Discussion on Supported Slices on E1 | Nokia, Nokia Shanghai Bell |
| R3-203852 | Clarification to 36.423 on the IE cellreservedforoperatoruse | Huawei, China Telecom, China Unicom |
| R3-203853 | Clarification to 36.423 on the IE cellreservedforoperatoruse | Huawei, China Telecom, China Unicom |
| R3-203854 | Clarification to 38.423 on the IE cellreservedforoperatoruse | Huawei, China Telecom, China Unicom |
| R3-203855 | Clarification to 38.423 on the IE cellreservedforoperatoruse | Huawei, China Telecom, China Unicom |
| R3-203856 | Clarification to 38.473 on the IE cellreservedforoperatoruse | Huawei, China Telecom, China Unicom |
| R3-203857 | Clarification to 38.473 on the IE cellreservedforoperatoruse | Huawei, China Telecom, China Unicom |
| R3-203863 | AMF Region Information in Xn setup procedure | ZTE, China Telecom,China Unicom |
| R3-203864 | AMF Region Information IE CR for Rel-15 38423 | ZTE, China Telecom,China Unicom |
| R3-203865 | AMF Region Information IE CR for Rel-16 38423 | ZTE, China Telecom,China Unicom |
| R3-203866 | RAN UE ID IE CR for Rel-16 38473 | ZTE, China Telecom,China Unicom |
| R3-203867 | RAN UE ID IE CR for Rel-15 38473 | ZTE, China Telecom,China Unicom |
| R3-203921 | Correction on DL RRC MESSAGE TRANSFER | CATT |
| R3-204054 | CB: # 85_NAS_non-delivery - Summay of offline discussion | Nokia - moderator |
| R3-204055 | Correction for UL UP TNL Information | Nokia, Nokia Shanghai Bell, ZTE, China Telecom, Samsung |
| R3-204056 | Correction for UL UP TNL Information | Nokia, Nokia Shanghai Bell, ZTE, China Telecom, Samsung |
| R3-204057 | CR to 38.463 on introducing a PDCP Status Report indication in PDCP-Configuration | China Telecom Corporation Ltd. |
| R3-204058 | CR to 38.463 on introducing a PDCP Status Report indication in PDCP-Configuration | China Telecom Corporation Ltd. |
| R3-204059 | CB: #folder name - Summary of discussion | China Telecom - moderator |
| R3-204060 | CB: # 87_5GS-_TAC_clarification - Summary of offline discussion | China Telecom - moderator |
| R3-204062 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson |
| R3-204063 | CB: # 88_n_of_supported_cells_exceeded - Summary of offline discussion | Ericsson - moderator |
| R3-204064 | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | Ericsson |
| R3-204065 | CB: # 89_OverlappingBandsHandling - Summary of offline discussion | Ericsson - moderator |
| R3-204066 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson |
| R3-204067 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204068 | CB: #90_MeasGapDeactivation - Summary of offline discussion | Ericsson -moderator |
| R3-204069 | Correstion on PDU Session Resrouce Modification Procedures | Ericsson |
| R3-204070 | Correstion on PDU Session Resrouce Modification Procedures | Ericsson |
| R3-204091 | Correction on RF parameters in NR cell information(X2AP) | CATT |
| R3-204092 | Correction on RF parameters in NR cell information(XnAP) | CATT |
| R3-204093 | Correction on RF parameters in NR cell information(F1AP) | CATT |
| R3-204094 | CB: #93_Hoprep_info - Summary of offline discussion | Nokia |
| R3-204095 | Correction on DL RRC MESSAGE TRANSFER | CATT |
| R3-204161 | Support of SN not broadcasting system information | Ericsson |
| R3-204162 | Support of SN not broadcasting system information | Ericsson |
| R3-204242 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-204243 | Correction of NAS NON Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-204258 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204259 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204260 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204261 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204290 | Correction for Handover Preparation Information | Nokia, Nokia Shanghai Bell |
| R3-204291 | Correction for Handover Preparation Information | Nokia, Nokia Shanghai Bell |
| R3-204310 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204311 | Measurement gap deactivation over F1AP CR 38.473 | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204314 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204328 | CB: # 87_5GS-_TAC_clarification - Summary of offline discussion | China Telecom - moderator |
| R3-204339 | Support of SN not broadcasting system information | Ericsson |
| R3-204340 | Support of SN not broadcasting system information | Ericsson |
| R3-204349 | PDCP Status Report indication in PDCP-Configuration | China Telecom, Huawei, CATT, ZTE, Intel Corporation |
| R3-204350 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204356 | PDCP Status Report indication in PDCP-Configuration | China Telecom, Huawei, CATT, ZTE, Intel Corporation |
| R3-204357 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204358 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204359 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204372 | CB: # 87_5GS-_TAC_clarification - Summary of offline discussion | China Telecom - moderator |
| R3-204374 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204375 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204385 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204386 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| R3-204387 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204388 | Update on semantics description of 5GS TAC and Served PLMN | ZTE, China Telecom, CATT |
| R3-204389 | Support of SN not broadcasting system information | Ericsson |
| R3-204390 | Support of SN not broadcasting system information | Ericsson |
| R3-204391 | Correction on RF parameters in NR cell information | CATT |
| R3-204392 | Correction on RF parameters in NR cell information | CATT |
| R3-204393 | Correction on RF parameters in NR cell information | CATT |
| R3-204521 | Correction on UE CONTEXT MODIFICATION REQUIRED message | ZTE, Samsung, China Telecom |
| R3-204522 | Correction of the Old QoS Flow List update during HO | Samsung, Ericsson |
| R3-204523 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-204524 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-204525 | Correstion on PDU Session Resrouce Modification Procedures | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204526 | Correstion on PDU Session Resrouce Modification Procedures | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204527 | Correction for Handover Preparation Information | Nokia, Nokia Shanghai Bell |
| R3-204528 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei, China Unicom |
| 9.3.8.2 | Pure Stage-2 Corrections | |
| R3-203144 | ANR enhancement for coexistence of SA and NSA deployment | LG Uplus, LG Electronics |
| R3-203167 | CR38.300 (Rel-15) ANR enhancement for coexistence of SA and NSA deployment | LG Uplus |
| R3-203168 | CR38.300 (Rel-16) ANR enhancement for coexistence of SA and NSA deployment | LG Uplus |
| R3-203169 | CR36.300 (Rel-15) Clarification of EN-DC TNL address discovery | LG Uplus, Huawei, Samsung |
| R3-203186 | CR36.300 (Rel-16) Clarification of EN-DC TNL address discovery | LG Uplus, Huawei, Samsung |
| R3-203194 | Change of SCTP association when current SCTP association is failed | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203195 | SCTP association change when current SCTP association is failed (NG) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203196 | SCTP association change when current SCTP association is failed (NG) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203197 | SCTP association change when current SCTP association is failed (F1) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203198 | SCTP association change when current SCTP association is failed (F1) | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203205 | Correction of F1 procedure in E1 Bearer Context Release scenario | Huawei, China Telecom, CMCC |
| R3-203206 | Correction of F1 procedure in E1 Bearer Context Release scenario | Huawei, China Telecom, CMCC |
| R3-203221 | Correction of UE-associated logical connection for E1 | Huawei, China Telecom, CMCC |
| R3-203222 | Correction of UE-associated logical connection for E1 | Huawei, China Telecom, CMCC |
| R3-203516 | Correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-203517 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-203518 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE |
| R3-203779 | Correction for RRC Reconfiguration Complete Indicator for the first reconfiguration after RRC re-establishment | Intel Corporation |
| R3-203780 | Correction for RRC Reconfiguration Complete Indicator for the first reconfiguration after RRC re-establishment | Intel Corporation |
| R3-203781 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation |
| R3-203782 | Adding missing steps querying the source DU’s latest configuration during the inter-gNB-DU mobility for intra-NR | Intel Corporation |
| R3-203889 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-203890 | SCTP association change when current SCTP association is failed | China Telcom, Nokia, Nokia Shanghai Bell |
| R3-203891 | SCTP association change when current SCTP association is failed | China Telecom, Nokia, Nokia Shanghai Bell |
| 10.1 | General | |
| R3-203014 | BLCR to 38.420: Addition of MDT feature | CMCC |
| R3-203015 | BLCR to 38.420: Addition of SON feature | CMCC |
| R3-203016 | BLCR to 38.470: Addition of SON feature | CMCC |
| R3-203017 | BLCR to 38.460: Addition of SON feature | CMCC |
| R3-203021 | MDT support for EN-DC | Huawei |
| R3-203023 | Addition of RACH Optimization Feature | CMCC, Huawei |
| R3-203025 | Addition of SON features | Huawei |
| R3-203026 | Addition of MDT feature | Huawei |
| R3-203027 | Addition of SON features | Ericsson |
| R3-203028 | Addition of MDT features | ZTE |
| R3-203029 | Addition of MDT features | Samsung |
| R3-203085 | Addition of SON feature | Huawei |
| R3-203086 | Addition of SON feature | CATT |
| R3-203087 | Addition of SON features | CMCC, Huawei |
| R3-203088 | Addition of SON features | Huawei |
| R3-203089 | Addition of SON features | Samsung |
| R3-203090 | Addition of SON features | Huawei |
| R3-203091 | Addition of MDT features | Samsung |
| R3-203092 | MDT Configuration support for XnAP | Ericsson |
| R3-203149 | MDT support for EN-DC | Huawei, SAMSUNG |
| R3-203899 | Updated work plan for SON and MDT WI | CMCC |
| R3-203952 | CB: # 1001_Email_SONMDT_BLs - Summary of email discussion | CMCC - moderator |
| R3-204024 | Addition of SON features | Ericsson |
| R3-204414 | BLCR to 38.420: Addition of MDT feature | CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204415 | BLCR to 38.420: Addition of SON feature | CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204416 | BLCR to 38.470: Addition of SON feature | CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204417 | BLCR to 38.460: Addition of SON feature | CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204421 | MDT support for EN-DC | Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTTDOCOMO |
| R3-204423 | Addition of SON features | CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204425 | Addition of SON features | Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204426 | Addition of MDT feature | Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTTDOCOMO |
| R3-204427 | Addition of MDT features | ZTE |
| R3-204428 | Addition of MDT features | Samsung, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Qualcomm Incorporated, LG Electronics, NTTDOCOMO |
| R3-204478 | Addition of SON feature | Huawei, CMCC ZTE, Nokia, Nokia Shanghai Bell,CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics |
| R3-204479 | Addition of SON feature | CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, LG Electronics, NTTDOCOMO |
| R3-204480 | Addition of SON features | CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell,CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204481 | Addition of SON features | Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204482 | Addition of SON features | Samsung, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Huawei, Qualcomm Incorporated, LG Electronics, Ericsson, NTT DOCOMO |
| R3-204483 | Addition of SON features | Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204484 | Addition of MDT features | Samsung, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204485 | MDT Configuration support for XnAP | Ericsson, CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Qualcomm Incorporated, LG Electronics, NTT DoCoMo |
| R3-204496 | MDT support for EN-DC | Huawei, Samsung, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm Incorporated, LG Electronics, NTTDOCOMO |
| R3-204502 | Addition of SON features | Ericsson, CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Qualcomm Incorporated, LG Electronics, NTT DoCoMo |
| R3-204520 | Addition of MDT features | ZTE, Nokia, Nokia Shanghai Bell, CMCC, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTTDOCOMO |
| 10.2.1.1 | Intra-System and Inter-System Connection Failure | |
| R3-203231 | (TP for SON BL CR for TS 38.300): Intra-System and Inter-System Connection Failure | Huawei |
| R3-203232 | (TP for SON BL CR for TS 36.300): Intra-System and Inter-System Connection Failure | Huawei |
| R3-203233 | (TP for SON BL CR for TS 36.413): Intra-System and Inter-System Connection Failure | Huawei |
| R3-203619 | (TP for SON BL CR for TS 38.423) Intra-System and Inter-System Connection Failure for MRO | Samsung, ZTE, CMCC |
| R3-203620 | (TP for SON BL CR for TS 38.413) Intra-System and Inter-System Connection Failure for MRO | Samsung, ZTE, CMCC |
| R3-203675 | (TP for SON BL CR for TS 38.423) Alignment of CGI coding for various SON features | CATT |
| R3-203871 | (TP for [NR_SON_MDT] BL CR for TS 38.300)Left issue on Stage 2 | ZTE |
| R3-203953 | CB: # 1002_Email_SONMDT_Conn_Failure - Summary of email discussion | Samsung - moderator |
| R3-204100 | (TP for SON BL CR for TS 38.300): Intra-System and Inter-System Connection Failure | Huawei |
| R3-204101 | (TP for SON BL CR for TS 38.423) Intra-System and Inter-System Connection Failure for MRO | Samsung, ZTE, CMCC |
| R3-204179 | CB: # 1002_Email_SONMDT_Conn_Failure - Summary of email discussion | Samsung - moderator |
| R3-204254 | (TP for SON BL CR for TS 38.413) Intra-System and Inter-System Connection Failure for MRO | Samsung, ZTE, CMCC |
| R3-204348 | (TP for SON BL CR for TS 38.300): Intra-System and Inter-System Connection Failure | Huawei |
| 10.2.1.2 | Inter-System Ping-Pong and Unnecessary Handover | |
| R3-203673 | (TP for SON BL CR for TS 36.413)Correction on inter-system unnecessary HO | CATT |
| R3-203674 | (TP for SON BL CR for TS 38.300)Correction on Inter-System Unnecessary Handover | CATT |
| R3-203954 | CB: # 1003_Email_SONMDR_PingPong - Summary of email discussion | CATT - moderator |
| R3-204105 | (TP for SON BL CR for TS 36.413)Correction on inter-system unnecessary HO | CATT |
| 10.2.1.4 | CU-DU Aspects for MRO | |
| R3-203307 | Addition of SON features CR 38.401 | Ericsson |
| R3-203388 | Signalling of RLF Report to gNB-DU TP 38.473 | Ericsson |
| R3-203389 | Signalling of RLF information from gNB-CU to gNB-DU | Ericsson |
| R3-203429 | Addition of SON features TP 38.470 | Ericsson |
| R3-203434 | Addition of SON features TP 38.470 | Ericsson |
| R3-203830 | Remaining issues for CU-DU MRO | LG Electronics |
| R3-203831 | (TP for NR_SON_MDT BL CR for TS 38.473) Remaining issues for CU-DU MRO | LG Electronics |
| R3-203832 | (TP for NR_SON_MDT BL CR for TS 38.470) Remaining issues for CU-DU MRO | LG Electronics |
| R3-203833 | (TP for NR_SON_MDT BL CR for TS 38.401) Remaining issues for CU-DU MRO | LG Electronics |
| R3-203872 | Left issue for CU-DU MRO | ZTE |
| R3-203873 | TP for [NR_SON_MDT] BL CR for TS 38.473) CU-DU MRO | ZTE |
| R3-203955 | CB: # 1004_Email_SONMDT_CUDU_MRO - Summary of email discussion | LG - moderator |
| R3-204319 | Addition of SON features CR 38.401 | Ericsson |
| R3-204320 | Addition of SON features TP 38.470 | Ericsson |
| 10.2.1.6 | UE Reported Mobility History | |
| R3-203234 | TP for UE reported history information in RRC-Restablisment for TS 38.423 | Huawei |
| R3-203956 | CB: # 1005_Email_SONMDR_UE_Mob_Hist - Summary of email discussion | Huawei - moderator |
| R3-204080 | TP for UE reported history information in RRC-Restablisment for TS 38.423 | Huawei |
| 10.2.2.1 | MLB for Xn/X2/F1/E1 | |
| R3-203235 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-203236 | (TP for SON BL CR for TS 38.423): MLB | Huawei |
| R3-203237 | (TP for SON BL CR for TS 36.423): MLB | Huawei |
| R3-203238 | (TP for SON BL CR for TS 38.463): MLB | Huawei |
| R3-203318 | (TP for SON BL CR for TS 38.463) Load reporting updates from RAN3#107bis-e | Nokia, Nokia Shanghai Bell |
| R3-203319 | Remaining open points for MLB | Nokia, Nokia Shanghai Bell |
| R3-203390 | MLB – TP for BL CR for 38.423 | Ericsson |
| R3-203391 | MLB – TP for BL CR for 38.473 | Ericsson |
| R3-203392 | MLB – TP for BL CR for 38.463 | Ericsson |
| R3-203393 | MLB – TP for BL CR for 36.423 | Ericsson |
| R3-203394 | Discussion on remaining FFS for MLB in Rel-16 | Ericsson |
| R3-203471 | Remaining issues on active UEs for MLB | NTTDOCOMO |
| R3-203473 | (TP for SON BL CR on 36.423) Addition of active UEs in load reporting | NTT DOCOMO, INC. |
| R3-203474 | (TP for SON BL CR on 38.423) Addition of active UEs in load reporting | NTT DOCOMO, INC. |
| R3-203475 | (TP for SON BL CR on 38.473) Addition of active UEs in load reporting | NTT DOCOMO, INC. |
| R3-203676 | Remaining Issues for MLB metrics | CATT |
| R3-203677 | (TP on SON BLCR for 38.423) TP on MLB metrics | CATT |
| R3-203678 | (TP on SON BLCR for 38.473) TP on MLB metrics | CATT |
| R3-203679 | (TP on SON BLCR for 36.423) TP on MLB metrics | CATT |
| R3-203803 | (TP for SON BL CR for TS 38.423) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-203804 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-203805 | (TP for SON BL CR for TS 38.473) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-203806 | (TP for SON BL CR for TS 36.423) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-203874 | Left Issues for MLB | ZTE |
| R3-203875 | TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of MLB Features | ZTE |
| R3-203876 | TP for [NR_SON_MDT] BL CR for TS 38.423) Addition of MLB Features | ZTE |
| R3-203877 | TP for [NR_SON_MDT] BL CR for TS 38.463) Addition of MLB Features | ZTE |
| R3-203878 | TP for [NR_SON_MDT] BL CR for TS 38.473) Addition of MLB Features | ZTE |
| R3-203900 | Remaining issues of MLB | CMCC |
| R3-203907 | TP to SON BLCR 38.423 on MLB | CMCC |
| R3-203928 | (TP for SON BL CR on 36.423) Addition of active UEs in load reporting | NTT DOCOMO, INC. |
| R3-203930 | (TP for SON BL CR on 38.423) Addition of active UEs in load reporting | NTT DOCOMO, INC. |
| R3-203931 | (TP for SON BL CR on 38.473) Addition of active UEs in load reporting | NTT DOCOMO, INC. |
| R3-203957 | CB: # 1006_Email_SONMDR_MLB - Summary of email discussion | Nokia - moderator |
| R3-204129 | CB: # 1006_Email_SONMDR_MLB - Summary of email discussion | Nokia - moderator |
| R3-204140 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-204154 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-204256 | (TP on SON BLCR for 36.423) TP on MLB metrics | CATT |
| R3-204336 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-204337 | MLB – TP for BL CR for 38.423 | Ericsson |
| R3-204344 | (TP on SON BLCR for 36.423) TP on MLB metrics | CATT |
| R3-204353 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT |
| 10.2.3.1 | RACH Optimization Enhancements | |
| R3-203397 | TP for PRACH Configuration IE Signalling on Xn Interface | Ericsson |
| R3-203494 | (TP for SON BL CR for TS 38.423): FFSes clean-up for PRACH configuration exchange | Huawei |
| R3-203495 | (TP for SON BL CR for TS 38.473): FFSes clean-up for PRACH configuration exchange | Huawei |
| R3-203540 | Discussion on the Remaining Issues for PRACH Optimization | China Telecom Corporation Ltd. |
| R3-203541 | TP for [NR_SON_MDT] BL CR for TS 36.423 | China Telecom, China Unicom, CATT, Huawei, ZTE |
| R3-203680 | Discussion on PRACH coordination | CATT |
| R3-203681 | (TP on SON BLCR for 38.423) TP on PRACH coordination | CATT |
| R3-203682 | (TP on SON BLCR for 38.473) TP on PRACH coordination | CATT |
| R3-203819 | Remaining issues for PRACH configuration transfer | Nokia, Nokia Shanghai Bell |
| R3-203879 | Left issue for PRACH configuraiton parameter | ZTE |
| R3-203904 | (TP for TS 38.470) on F1 aspects for SON | CMCC |
| R3-203905 | (TP for TS 38.420) on Xn aspects for SON | CMCC |
| R3-203958 | CB: # 1007_Email_SONMDT_RACH - Summary of email discussion | China Telecom - moderator |
| R3-204137 | (TP for SON BL CR for TS 38.473): FFSes clean-up for PRACH configuration exchange | Huawei |
| R3-204257 | (TP on SON BLCR for 38.423) TP on PRACH coordination | CATT |
| R3-204262 | TP for [NR_SON_MDT] BL CR for TS 36.423 | China Telecom, China Unicom, CATT, Huawei, ZTE |
| R3-204304 | CB: # 1007_Email_SONMDT_RACH - Summary of email discussion | China Telecom - moderator |
| R3-204305 | (TP for TS 38.420) on Xn aspects for SON | CMCC |
| R3-204313 | TP for [NR_SON_MDT] BL CR for TS 36.423 | China Telecom, China Unicom, CATT, Huawei, ZTE |
| R3-204326 | (TP for SON BL CR for TS 38.473): FFSes clean-up for PRACH configuration exchange | Huawei |
| R3-204362 | TP for [NR_SON_MDT] BL CR for TS 36.423 | China Telecom, China Unicom, CATT, Huawei, ZTE |
| R3-204363 | CB: # 1007_Email_SONMDT_RACH - Summary of email discussion | China Telecom - moderator |
| R3-204376 | TP for [NR_SON_MDT] BL CR for TS 36.423 | China Telecom, China Unicom, CATT, Huawei, ZTE |
| R3-204377 | (TP on SON BLCR for 38.423) TP on PRACH coordination | CATT |
| 10.2.3.2 | Configuration Conflicts for RACH Optimization | |
| R3-203395 | TP for RACH report availability indication on F1 interface | Ericsson |
| R3-203396 | TP for RACH Report Signalling on F1 Interface | Ericsson |
| R3-203398 | Solution for RACH Conflict Detection and Resolution at gNB-DU | Ericsson |
| R3-203496 | (TP for SON BL CR for TS 38.423): UE RACH report for RACH optimization | Huawei |
| R3-203497 | (TP for SON BL CR for TS 38.473):UE RACH report for RACH optimization | Huawei |
| R3-203625 | (TP for SON BL CR for TS 38.473) RACH Report over F1 Interface | Samsung |
| R3-203626 | (TP for SON BL CR for TS 38.423) RACH Report over F1 Interface | Samsung |
| R3-203820 | Remaining issues for RACH conflict resolution | Nokia, Nokia Shanghai Bell |
| R3-203821 | (TP for SON BL CR for TS 38.473) Introduction of RACH Assistance Information | Nokia, Nokia Shanghai Bell |
| R3-203822 | (TP for SON BL CR for TS 38.423) Introduction of RACH Assistance Information | Nokia, Nokia Shanghai Bell |
| R3-203880 | Configuration Conflicts for RACH Optimization | ZTE |
| R3-203881 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Left issue for RACH Report from UE | ZTE |
| R3-203959 | CB: # 1008_Email_SONMDT_RACH_Config - Summary of email discussion | Huawei - moderator |
| R3-204138 | (TP for SON BL CR for TS 38.423): UE RACH report for RACH optimization | Huawei |
| R3-204139 | (TP for SON BL CR for TS 38.473):UE RACH report for RACH optimization | Huawei |
| R3-204187 | CB: # 1008_Email_SONMDT_RACH_Config - Summary of email discussion | Huawei - moderator |
| 10.3.1 | MDT Activation and Reporting | |
| R3-203337 | Streaming based MDT | Qualcomm Incorporated |
| R3-203338 | (TP for MDT BL CR for TS 38.413) Streaming based MDT | Qualcomm Incorporated |
| R3-203339 | (TP for MDT BL CR for TS 38.423) Streaming based MDT | Qualcomm Incorporated |
| R3-203399 | Averaging interval in M6 measurement configuration on NGAP | Ericsson |
| R3-203400 | Averaging interval in M6 measurement configuration on XnAP | Ericsson |
| R3-203401 | Averaging interval in M6 measurement configuration on F1AP | Ericsson |
| R3-203402 | Averaging interval in M6 measurement configuration on E1AP | Ericsson |
| R3-203498 | (TP for MDT BL CR for TS 38.413): Corrections to MDT BLCR (resubmission of R3-202785) | Huawei |
| R3-203499 | (TP for MDT BL CR for TS 38.413): Clean up FFSes in MDT BLCR | Huawei |
| R3-203500 | (TP for MDT BL CR for TS 38.423): Clean up FFSes in MDT BLCR | Huawei |
| R3-203501 | Beam related configuration for immediate MDT | Huawei, LGU+, BT |
| R3-203502 | (TP for MDT BL CR for TS 38.413): Beam related configuration for immediate MDT | Huawei, LGU+, BT |
| R3-203503 | (TP for MDT BL CR for TS 38.423): Beam related configuration for immediate MDT | Huawei, LGU+, BT |
| R3-203504 | [DRAFT] LS on SSB based Beam configurations for immediate MDT | Huawei |
| R3-203669 | (TP for MDT BL CR for 38.473) Correction for Cell Traffic Trace message and MDT configuration | Samsung R&D Institute UK |
| R3-203670 | (TP for MDT BL for 38.423) Propagation for Management Based MDT PLMN List | Samsung R&D Institute UK |
| R3-203807 | On Rel-16 MDT status | Nokia, Nokia Shanghai Bell |
| R3-203808 | (TP for MDT BL CRs) URI for Streaming Trace reporting on NG, Xn, F1 and E1 | Nokia, Nokia Shanghai Bell |
| R3-203882 | Left issue for MDT | ZTE |
| R3-203883 | (TP for [NR_SON_MDT] BL CR for TS 38.413)Addition of MDT | ZTE |
| R3-203884 | (TP for [NR_SON_MDT] BL CR for TS 38.423)Addition of MDT | ZTE |
| R3-203885 | (TP for [NR_SON_MDT] BL CR for TS 38.463)Addition of MDT | ZTE |
| R3-203886 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Addition of MDT | ZTE |
| R3-203902 | BLCR for TS 38.470)_Addtion of MDT features | CMCC |
| R3-203903 | BLCR for TS 38.460_Addtion of MDT features | CMCC |
| R3-203906 | (TP for TS 38.413) on corrections of WLAN and BT configuration | CMCC |
| R3-203960 | CB: # 1009_Email_SONMDT_MDT - Summary of email discussion | Qualcomm - moderator |
| R3-204106 | (TP for MDT BL CR for 38.473) Correction for Cell Traffic Trace message and MDT configuration | Samsung R&D Institute UK |
| R3-204110 | Support for Streaming Based MDT And Trace report | ZTE |
| R3-204111 | (TP for [NR_SON_MDT] BL CR for TS 38.413)Addition of MDT | ZTE |
| R3-204112 | (TP for [NR_SON_MDT] BL CR for TS 38.423)Addition of MDT | ZTE |
| R3-204113 | (TP for [NR_SON_MDT] BL CR for TS 38.463)Addition of MDT | ZTE |
| R3-204264 | [DRAFT] LS on propagation of user consent related information during Xn inter-PLMN handover | Nokia, Nokia Shanghai Bell |
| R3-204295 | CB: # 1009_Email_SONMDT_MDT - Summary of email discussion | Qualcomm - moderator |
| R3-204330 | CB: # 1009_Email_SONMDT_MDT - Summary of email discussion | Qualcomm - moderator |
| R3-204378 | LS on propagation of user consent related information during Xn inter-PLMN handover | Nokia, Nokia Shanghai Bell |
| R3-204500 | BLCR to 38.470: Addition of MDT feature | CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| R3-204501 | BLCR to 38.460: Addition of MDT feature | CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Huawei, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO |
| 10.3.2 | MDT for Inactive UEs | |
| R3-203340 | Prioritization of Signaling MDT over management based MDT for different RRC states | Qualcomm Incorporated |
| R3-203341 | (TP for MDT BL CR for TS 38.413) Prioritization of Signaling MDT over management based MDT for different RRC states | Qualcomm Incorporated |
| R3-203342 | (TP for MDT BL CR for TS 38.423) Prioritization of Signaling MDT over management based MDT for different RRC states | Qualcomm Incorporated |
| R3-203404 | Signalling Logged MDT configuration indication over XnAP | Ericsson |
| R3-203405 | Signalling Logged MDT configuration indication over NGAP TP | Ericsson |
| R3-203671 | (TP for 38.423)management based logged MDT not overwrite the signalling based logged MDT | Samsung R&D Institute UK |
| R3-203672 | (TP for 38.413)management based logged MDT not overwrite the signalling based logged MDT | Samsung R&D Institute UK |
| R3-203887 | Management based MDT should not overwrite signalling based MDT | ZTE |
| R3-203950 | (Response to R3-203404) About the solution to avoid the overwrite problem-XnAP | BEIJING SAMSUNG TELECOM R&D |
| R3-203951 | (Response to R3-203404) About the solution to avoid the overwrite problem-NGAP | BEIJING SAMSUNG TELECOM R&D |
| R3-203961 | CB: # 1010_Email_SONMDT_MDT_INACTIVE - Summary of email discussion | Ericsson - moderator |
| R3-204308 | CB: # 1010_Email_SONMDT_MDT_INACTIVE - Summary of email discussion | Ericsson - moderator |
| 10.3.3 | MDT for MR-DC | |
| R3-203403 | M4 measurements configuration for Immediate MDT with EN-DC | Ericsson |
| R3-203888 | M4 measuement for EN-DC MDT | ZTE |
| R3-203962 | CB: # 1011_Email_SONMDT_EN-DC - Summary of email discussion | ZTE - moderator |
| R3-204114 | M4 measurement for EN-DC | ZTE |
| R3-204115 | limitation of propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE |
| R3-204202 | CB: # 1011_Email_SONMDT_EN-DC - Summary of email discussion | ZTE - moderator |
| 13.1 | General | |
| R3-203002 | BL CR to 38.423: Support for IAB | Samsung |
| R3-203003 | BL CR to 38.463: Support for IAB | Huawei |
| R3-203004 | BL CR to 36.413: Support for IAB | Huawei |
| R3-203005 | BL CR to 38.413: Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-203018 | Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-203036 | BL CR to 36.420: Support for IAB | Samsung |
| R3-203037 | BL CR to 38.425: Support for IAB | Samsung |
| R3-203066 | BL CR to 36.423: Support for IAB | Samsung |
| R3-203067 | BL CR to 38.401 Support for IAB | Huawei |
| R3-203068 | BL CR to 38.470: Support for IAB | Ericsson |
| R3-203069 | BL CR to 38.473: Support for IAB | Ericsson |
| R3-203099 | draftCR TS 38.300 Mapping of Uplink Traffic to Backhaul RLC Channels | Ericsson |
| R3-203963 | CB: # 1_IAB_BLs - Summary of email discussion | Qualcomm - moderator |
| R3-204096 | CB: # 1_IAB_BLs - Summary of email discussion | Qualcomm - moderator |
| R3-204097 | draftCR TS 38.300 Mapping of Uplink Traffic to Backhaul RLC Channels | Ericsson |
| R3-204402 | BL CR to 38.423: Support for IAB | Samsung, Nokia, Nokia Shanghai Bell |
| R3-204403 | BL CR to 38.463: Support for IAB | Huawei, Nokia, Nokia Shanghai Bell,Samsung |
| R3-204404 | BL CR to 36.413: Support for IAB | Huawei, Nokia, Nokia Shanghai Bell |
| R3-204405 | BL CR to 38.413: Support for IAB | Nokia, Nokia Shanghai Bell, Huawei |
| R3-204418 | Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-204434 | BL CR to 36.420: Support for IAB | Samsung, Nokia, Nokia Shanghai Bell |
| R3-204435 | BL CR to 38.425: Support for IAB | Samsung, Nokia, Nokia Shanghai Bell |
| R3-204461 | BL CR to 36.423: Support for IAB | Samsung |
| R3-204462 | BL CR to 38.401 Support for IAB | Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-204463 | BL CR to 38.470: Support for IAB | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204464 | BL CR to 38.473: Support for IAB | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, ZTE |
| R3-204519 | BL CR to 36.423: Support for IAB | Samsung, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| 13.2.1.1 | IAB Node Integration | |
| R3-203813 | (TP for NR-IAB BL CR for TS 36.413): Correction to BL CR | Ericsson |
| R3-203814 | (TP for NR-IAB BL CR for TS 38.413): Correction to BL CR | Ericsson |
| R3-203815 | (TP for NR-IAB BL CR for TS 36.423): Correction to BL CR | Ericsson |
| R3-203816 | (TP for NR-IAB BL CR for TS 38.423): Correction to BL CR | Ericsson |
| R3-203923 | (TP for NR-IAB BL CR for 38.473) Discussion on IAB barred Cell | Samsung Electronics Nordic AB |
| R3-203964 | CB: # 3_IAB_optE-RAB_setup-relatedIEs - Summary of email discussion | Ericsson - moderator |
| R3-203965 | CB: # 4_IAB_BarredCell - Summary of email discussion | Samsung - moderator |
| R3-204081 | (TP for NR-IAB BL CR for TS 36.413): Correction to BL CR | Ericsson |
| R3-204082 | (TP for NR-IAB BL CR for TS 38.413): Correction to BL CR | Ericsson |
| R3-204083 | (TP for NR-IAB BL CR for TS 36.423): Correction to BL CR | Ericsson |
| R3-204084 | (TP for NR-IAB BL CR for TS 38.423): Correction to BL CR | Ericsson |
| R3-204088 | (TP for NR-IAB BL CR for 38.473) Discussion on IAB barred Cell | Samsung Electronics Nordic AB |
| R3-204098 | (TP for NR-IAB BL CR for TS 38.401): Corrections to BL CR | Ericsson |
| R3-204360 | (TP for NR_IAB BL CR for TS 38.401) : 2 mappings matching | Nokia, Qualcomm |
| R3-204381 | (TP for NR-IAB BL CR for TS 38.401): Corrections to BL CR | Ericsson |
| R3-204382 | (TP for NR_IAB BL CR for TS 38.401) : 2 mappings matching | Nokia, Qualcomm |
| 13.2.1.2 | Adaptation, QoS, Bearer Setup | |
| R3-203151 | (TP for NR_IAB BL CR for TS 38.473): Mapping configuration in donor DU and intermediate node | ZTE, Sanechips |
| R3-203152 | Discussion on mapping configuration in donor DU and intermediate node | ZTE, Sanechips |
| R3-203343 | (TP for NR_IAB BL CR TS 38473) IAB DL traffic mapping and BH RLC channel mapping configuration | Qualcomm Incorporated |
| R3-203344 | (TP for NR_IAB BL CR TS 38300) IAB stage-2 clean up | Qualcomm Incorporated |
| R3-203612 | (TP for NR-IAB BL CR for 38.473) Signaling design for bearer mapping configuration | Samsung |
| R3-203613 | (TP for NR-IAB BL CR for 38.473) Remaining issues for F1AP | Samsung |
| R3-203704 | (TP for NR-IAB BL CR for TS 38.473) BH RLC channel mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell, Huawei |
| R3-203817 | CR 38.472 Handling of SCTP Transport for IAB-MTs in INACTIVE State | Ericsson |
| R3-203818 | (TP for NR-IAB BL CR for TS 38.473): Correction of BH RLC CH ID | Ericsson |
| R3-203842 | Discussion on IAB inactive | Huawei |
| R3-203843 | (TP for NR-IAB BL CR for TS 38.473): Miscellaneous correction for F1AP | Huawei |
| R3-203916 | (TP for NR-IAB BL CR for TS 38.473) BH RLC channel mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell, Huawei |
| R3-203966 | CB: # 5_IAB_BH_RLC_CH_ID - Summary of email discussion | Ericsson - moderator |
| R3-203967 | CB: # 6_IAB_bearer_mapping - Summary of email discussion | Nokia - moderator |
| R3-203968 | CB: # 7_IAB_BH_misc_cleanups - Summary of email discussion | Huawei - moderator |
| R3-203969 | CB: # 8_IAB_MT_INACTIVE - Summary of email discussion | Ericsson - moderator |
| R3-204075 | CR 38.472 Handling of SCTP Transport for IAB-MTs in INACTIVE State | Ericsson |
| R3-204099 | CB: # 6_IAB_bearer_mapping - Summary of email discussion | Nokia - moderator |
| R3-204169 | CR 38.472 Handling of SCTP Transport for IAB-MTs in INACTIVE State | Ericsson |
| R3-204244 | (TP for NR-IAB BL CR for TS 38.401) Traffic mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell |
| R3-204245 | (TP for NR-IAB BL CR for TS 38.473) Traffic mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell |
| R3-204248 | (TP for NR-IAB BL CR for TS 38.473): Miscellaneous correction for F1AP | Huawei |
| R3-204249 | (TP for NR_IAB BL CR TS 38300) IAB stage-2 clean up | Qualcomm Incorporated |
| R3-204287 | Draft LS on multiple UL BH mapping for F1-C | Huawei |
| R3-204298 | (TP for NR-IAB BL CR for TS 38.401): Handling of IAB-DU F1 Connection for IAB-MTs in INACTIVE State | Ericsson |
| R3-204322 | (TP for NR-IAB BL CR for TS 38.401): Handling of IAB-DU F1 Connection for IAB-MTs in INACTIVE State | Ericsson |
| R3-204345 | LS on multiple UL BH mapping for F1-C | Huawei |
| 13.2.1.3 | IP Address Management | |
| R3-203614 | (TP for NR-IAB BL CR for 38.401) Remaining issues on IP address management | Samsung |
| R3-203615 | (TP for NR-IAB BL CR for 38.473) Remaining issues on IP address management | Samsung |
| R3-203970 | CB: # 9_IAB_IPaddr_alloc_SA - Summary of email discussion | Samsung - moderator |
| R3-204078 | (TP for NR-IAB BL CR for 38.401) Remaining issues on IP address management | Samsung |
| R3-204079 | (TP for NR-IAB BL CR for 38.473) Remaining issues on IP address management | Samsung |
| 13.2.1.4 | IAB-Specific Physical Layer Parameter Handling in F1AP | |
| R3-203104 | LS on IAB-DU features | 3GPP RAN1 |
| R3-203150 | Considerations on IAB-DU features | ZTE, Sanechips |
| R3-203153 | (TP for NR_IAB BL CR for TS 38.473): PHY Layer parameters configuration | ZTE, Sanechips |
| R3-203762 | Discussion on IAB-DU Layer-1 Features | AT&T |
| R3-203840 | (TP for NR-IAB BL CR for TS 38.473):Remianing issue for IAB resource configuration | Huawei |
| R3-203971 | CB: # 2_IAB-DU_features_and_PHY_parameters - Summary of email discussion | ZTE - moderator |
| R3-204306 | (TP for NR_IAB BL CR for TS 38.473): PHY Layer parameters configuration | ZTE, Sanechips |
| 13.2.4 | DC Operation with IAB | |
| R3-203154 | Discussion on IP address assignment for F1-C over LTE leg | ZTE, Sanechips |
| R3-203345 | IP address allocation procedure for F1-C over LTE/X2 in IAB | Qualcomm Incorporated |
| R3-203616 | (TP for NR-IAB BL CR for 38.401) Discussion on IP address allocation for LTE leg | Samsung |
| R3-203702 | IAB IP address management in NSA | Nokia, Nokia Shanghai Bell |
| R3-203703 | Discussion on F1-C over LTE leg or NR leg | Nokia, Nokia Shanghai Bell |
| R3-203841 | Remaining issue of F1AP over LTE | Huawei |
| R3-203972 | CB: # 10_IAB_DCoperation - Summary of email discussion | Nokia - moderator |
| R3-204153 | [Draft] LS on IAB F1-C traffic transfer for NSA IAB | Nokia |
| R3-204165 | LS on IAB F1-C traffic transfer for NSA IAB | Nokia |
| R3-204246 | (TP for NR-IAB BL CR for TS 38.401) IAB DC operation | Nokia, Nokia Shanghai Bell |
| R3-204247 | (TP for NR_IAB BL CR for TS36.423): IAB IP address signaling via X2 in EN-DC | Huawei |
| 13.3.2.1 | Functions and Criteria | |
| R3-203778 | (TP for NR-IAB BL CR for 38.401) Correction on intra-CU topological redundancy procedure | Intel Corporation |
| R3-203839 | (TP for NR-IAB BL CR for TS 38.401) : Miscellaneous stage 2 change for IAB BL CR to 38.401 | Huawei |
| R3-203973 | CB: # 11_IAB_migration_functions - Summary of email discussion | Intel - moderator |
| R3-204250 | (TP for NR-IAB BL CR for TS 38.401) : Miscellaneous stage 2 change for IAB BL CR to 38.401 | Huawei |
| 13.3.2.2 | Under the Same Donor | |
| R3-203155 | (TP for NR_IAB BL CR for TS 38.401): Intra-CU migration | ZTE, Sanechips |
| R3-203156 | (TP for NR_IAB BL CR for TS 38.473): UP TNL Information update in intra-CU migration scenario | ZTE, Sanechips |
| R3-203346 | (TP for NR_IAB BL CR TS 38.401) IAB topology adaptation and redundancy clean up | Qualcomm Incorporated |
| R3-203525 | (TP for NR_IAB BL CR for TS38.463) DL UP TNL update | CATT |
| R3-203617 | (TP for NR-IAB BL CR for 38.473) Discussion on the UP information update during migration | Samsung |
| R3-203618 | (TP for NR-IAB BL CR for 38.463) Discussion on the UP information update during migration | Samsung |
| R3-203844 | (TP for NR_IAB BL CR for TS38.463) TNL information update when IAB topology update | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203845 | (TP for NR-IAB BL CR for TS 38.473):BAP configuration and TNL information update when IAB topology change | Huawei |
| R3-203946 | Response to: Response to R3-203525, R3-203844-5, R3-203617-8, R3-203155-6, R3-203916, R3-203343, R3-203612, R3-203151-2 | Ericsson Japan K.K. |
| R3-203974 | CB: # 12_IAB_migration_same_donor - Summary of email discussion | Huawei |
| R3-204251 | (TP for NR_IAB BL CR for TS 38.401): IAB topology update | Huawei |
| R3-204252 | (TP for NR_IAB BL CR for TS38.463) TNL information update when IAB topology update | Huawei, Huawei, Nokia, Nokia Shanghai Bell |
| R3-204253 | (TP for NR-IAB BL CR for TS 38.473):BAP configuration and TNL information update when IAB topology change | Huawei |
| R3-204323 | (TP for NR_IAB BL CR for TS 38.401): IAB topology update | Huawei |
| R3-204346 | CB: # 12_IAB_migration_same_donor - Summary of email discussion | Huawei |
| R3-204347 | (TP for NR-IAB BL CR for TS 38.473):BAP configuration and TNL information update when IAB topology change | Huawei |
| R3-204383 | (TP for NR-IAB BL CR for TS 38.473):BAP configuration and TNL information update when IAB topology change | Huawei |
| R3-204384 | (TP for NR_IAB BL CR for TS38.463) TNL information update when IAB topology update | Huawei, Huawei, Nokia, Nokia Shanghai Bell |
| 14.1 | General | |
| R3-203006 | Introduction of NBIOT dedicated CP functions when connected to 5GC | Nokia, Nokia Shanghai Bell |
| R3-203007 | Introduction of Suspend-Resume for 5GC | Nokia, Nokia Shanghai Bell |
| R3-203008 | Introduction of CP UP NB-IoT Others | Huawei |
| R3-203012 | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | LG Electronics |
| R3-203013 | CR for 36.423 on NB-IoT PRACH configuration exchange over X2AP | ZTE, Ericsson, Huawei |
| R3-203019 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-203020 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-203030 | Introduction of eMTC connected to 5GC | Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-203035 | CR 36.413 for Support NB-IoT UE Specific DRX | ZTE, Huawei, Vodafone |
| R3-203049 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson, Huawei, Qualcomm Incorporated |
| R3-203050 | Common CP/UP aspects of CIoT UEs when connected to 5GC | Ericsson, ZTE |
| R3-203051 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-203052 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-203053 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated |
| R3-203054 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson |
| R3-203055 | Introduction of eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG, Nokia, Nokia Shanghai Bell |
| R3-203056 | Introduction of NB-IoT related NG-AP procedures | Huawei |
| R3-203057 | Introduction of CP UP NB-IoT Others | Huawei |
| R3-203148 | Support of WUS Group | Huawei, Vodafone, Ericsson, ZTE |
| R3-203725 | Clarification on BL CRs structure for final agreement | Ericsson |
| R3-203909 | (TP to NGAP BL CR#0120 “Introduction of NB-IoT Paging and eDRX aspects”) Correction of asn.1 | Huawei |
| R3-203910 | (TP to NGAP BL CR#0153 “Common CP/UP aspects of CIoT UEs when connected to 5GC”) Correction of asn.1 | Huawei |
| R3-203975 | CB: # NBIOT_MTC1-MTC_NB-IoT_BLs - Summary of email discussion | Ericsson - moderator |
| R3-204406 | Introduction of NBIOT dedicated CP functions when connected to 5GC | Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-204407 | Introduction of Suspend-Resume for 5GC | Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-204408 | Introduction of CP UP NB-IoT Others | Huawei, ZTE |
| R3-204412 | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | LG Electronics, Nokia, Nokia Shanghai Bell, Huawei |
| R3-204413 | CR for 36.423 on NB-IoT PRACH configuration exchange over X2AP | ZTE, Ericsson, Huawei |
| R3-204419 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-204420 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-204429 | Introduction of eMTC connected to 5GC | Huawei, Nokia, Nokia Shanghai Bell, CMCC, ZTE |
| R3-204433 | Support NB-IoT UE Specific DRX | ZTE, Huawei, Vodafone |
| R3-204446 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE |
| R3-204447 | Common CP/UP aspects of CIoT UEs when connected to 5GC | Ericsson, ZTE, Nokia, Nokia Shanghai Bell |
| R3-204448 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-204449 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson, ZTE |
| R3-204450 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE |
| R3-204451 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-204452 | Introduction of eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG, Nokia, Nokia Shanghai Bell |
| R3-204453 | Introduction of NB-IoT related NG-AP procedures | Huawei, ZTE |
| R3-204454 | Introduction of CP UP NB-IoT Others | Huawei, ZTE |
| R3-204495 | Support of WUS Group | Huawei, Vodafone, Ericsson, ZTE |
| R3-204514 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson, ZTE |
| 14.3.2.3 | Support for Coverage Enhancement | |
| R3-203446 | (TP for baseline CR153 on “Common CP/UP aspects of CIoT UEs when connected to 5GC”) Correction of Coverage Enhancement for Paging | Nokia, Nokia Shanghai Bell |
| 14.3.2.4 | Update of Connection Establishment Indication | |
| R3-203542 | (TP to 38.410 BL CR0020 “Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2)”) Update of Connection Establishment Indication | Huawei |
| R3-203976 | CB: # NBIOT_MTC2-CE_and_CEI - Summary of email discussion | Nokia - moderator |
| 14.3.2.5 | Immediate Transition to Suspension | |
| R3-203347 | (TP to BL CR#0188 / 38.413 on Suspend-Resume) Removal of editor’s note in immediate transition to suspension | Qualcomm Incorporated |
| R3-203447 | (TP for baseline CR188 on “suspend resume for 38.413”) Correction of Immediate Suspension | Nokia, Nokia Shanghai Bell |
| R3-203915 | TP to BL CR#0188 “Introduction of Suspend-Resume for 5GC (UP common part)” for TS 38.413: Support of MO-EDT for UP CIoT 5GS optimization | LG Electronics |
| R3-203944 | Response to R3-203347,R3-203447, R3-203915 | Ericsson Telecomunicazioni SpA |
| R3-203977 | CB: # NBIOT_MTC3-Immediate_Transition_to_Suspension - Summary of email discussion | LG - moderator |
| R3-204121 | (TP for baseline CR188 on “suspend resume for 38.413”) Correction of Immediate Suspension | Nokia, Nokia Shanghai Bell |
| 14.3.2.6 | Pending Data and UE Differentiation | |
| R3-203448 | (TP for baseline CR188 on “suspend resume for 38.413”) Correction of Resume with Pending Data Indication | Nokia, Nokia Shanghai Bell |
| R3-203726 | Clarification on the use of Pending Data indication and UE Differentiation Information for UP CIoT 5GS Optimization | Ericsson |
| R3-203727 | (TP for BL CR# 0153 - Common CP/UP aspects of CIoT UEs when connected to 5GC for 38.413): Addition of UE Differentiation Information | Ericsson |
| R3-203728 | (TP for BL CR# 0153 - Common CP/UP aspects of CIoT UEs when connected to 5GC for 38.413): Addition of Pending Data Indication | Ericsson |
| R3-203729 | LS on addition of the Pending Data Indication to 5GS | Ericsson |
| R3-203948 | Response to R3-203448 and R3-203726 | Qualcomm Incorporated |
| R3-203978 | CB: # NBIOT_MTC4-Pendingdata_UEdiffer - Summary of email discussion | Ericsson - moderator |
| R3-204152 | LS on addition of the Pending Data Indication to 5GS | Ericsson |
| 14.3.2.9 | Others | |
| R3-203107 | LS on early UE capability retrieval for eMTC | 3GPP RAN2 |
| R3-203179 | (TP to BL CR #0156 NB-IoT NG-AP procedures) early UE capability retrieval for eMTC | ZTE |
| R3-203180 | CR 36.413 early UE capability retrieval for eMTC | ZTE |
| R3-203216 | Consideration on early UE capability retrieval for eMTC | Huawei |
| R3-203217 | [DRAFT] Reply LS on early UE capability retrieval for eMTC | Huawei |
| R3-203225 | (TP to NGAP BL CR#0156 “Introduction of NB-IoT related NG-AP procedures”) Criticality of the new introduced Messages | Huawei |
| R3-203226 | (TP to NGAP BL CR#0173 “Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC”) Criticality of AMF CP RELOCATION INDICATION | Huawei |
| R3-203267 | (TP to NGAP BL CR0188 “Introduction of Suspend-Resume”) RRC Resume Cause | Huawei |
| R3-203350 | Early UE Capability Retrieval for eMTC | Qualcomm Incorporated |
| R3-203351 | [DRAFT] Reply LS on early UE capability retrieval for eMTC | Qualcomm Incorporated |
| R3-203352 | Support for early retrieval of UE capabilities | Qualcomm Incorporated |
| R3-203353 | Support for early retrieval of UE capabilities | Qualcomm Incorporated |
| R3-203354 | (TP to BL CR#0173 / 38.413 on CP-CIoT 5GS) Support for early retrieval of UE capabilities | Qualcomm Incorporated |
| R3-203449 | (TP for baseline CR153 on “Common CP/UP aspects of CIoT UEs when connected to 5GC”) Correction of Baseline CR153 | Nokia, Nokia Shanghai Bell |
| R3-203450 | (TP for baseline CR188 on “suspend resume for 38.413”) Correction of Extended Time | Nokia, Nokia Shanghai Bell |
| R3-203979 | CB: # NBIOT_MTC5-Early_UE_Capability_Retrieval - Summary of email discussion | Qualcomm - moderator |
| R3-203980 | CB: # NBIOT_MTC6-others - Summary of email discussion | Huawei - moderator |
| R3-204072 | CR 36.413 early UE capability retrieval for eMTC | ZTE |
| R3-204102 | (TP for baseline CR188 on “suspend resume for 38.413”) Correction of Extended Time | Nokia, Nokia Shanghai Bell |
| 14.5.1 | Group WUS | |
| R3-203181 | (TP to BL CR#1762 Support of WUS Group) FFS Removal for Paging Probability Information value range | ZTE |
| R3-203214 | (TP to NGAP BL CR#0153 “Common CP/UP aspects of CIoT UEs when connected to 5GC”) Support of Group WUS when connecting to 5GC | Huawei, Vodafone |
| R3-203215 | (TP to S1AP CR#1762 “Support of WUS Group”) Remove the Editor Note and FFS | Huawei, Vodafone |
| R3-203451 | (TP for baseline CR1762 on “support of WUS group”) Correction of Group WUS information in S1AP | Nokia, Nokia Shanghai Bell |
| R3-203452 | (TP for baseline CR153 on “common CP/UP aspects of CIoT UEs when connected to 5GC” NGAP) Correction of Group WUS information in NGAP | Nokia, Nokia Shanghai Bell |
| R3-203730 | Clarification on WUS grouping remaining issues | Ericsson |
| R3-203731 | [Draft] Reply LS on assistance indication for WUS | Ericsson |
| R3-203732 | (TP to S1AP BL CR #1762): Support of WUS Group | Ericsson |
| R3-203981 | CB: # NBIOT_MTC7-Group_WUS - Summary of email discussion | ZTE - moderator |
| 15.1 | General | |
| R3-203009 | Baseline CR for introducing Rel-16 LTE further mobility enhancement | Intel Corporation |
| R3-203010 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-203033 | CR for introducing Rel-16 NR mobility enhancement | CATT, CMCC |
| R3-203034 | TS38.470 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-203042 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-203058 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-203059 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-203078 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom |
| R3-203079 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation, CATT, ZTE, Huawei |
| R3-203080 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-203081 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, CATT |
| R3-203100 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, Nokia, Nokia Shanghai Bell |
| R3-203101 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | CATT, Nokia, Nokia Shanghai Bell |
| R3-203145 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Refine X2AP Abnormal Conditions etc | ZTE |
| R3-203146 | (TP for NR_Mob_enh BL CR for TS 38.423) Refine XnAP Abnormal Conditions etc | ZTE |
| R3-203147 | (TP for NR_Mob_enh BL CR for TS 37.340) Concluding Rel-16 DAPS and Conditional Mobility in MR-DC Scenarios | ZTE |
| R3-203562 | Correction of Baseline CR R3-203100 for introducing Rel-16 NR mobility enhancement | CATT |
| R3-203563 | Correction of Baseline CR R3-203101 for introducing Rel-16 LTE further mobility enhancements | CATT |
| R3-203763 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Clean-up on 8.9.4 from the last agreed R3-202823 | Intel Corporation |
| R3-203982 | CB: # 31_MobEnh_BLs - Summary of email discussion | Intel - moderator |
| R3-204122 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Refine X2AP Abnormal Conditions etc | ZTE |
| R3-204123 | (TP for NR_Mob_enh BL CR for TS 38.423) Refine XnAP Abnormal Conditions etc | ZTE |
| R3-204205 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-204225 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-204409 | Baseline CR for introducing Rel-16 LTE further mobility enhancement | Intel Corporation |
| R3-204410 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-204431 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, CMCC |
| R3-204432 | TS38.470 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom, Intel Corporation |
| R3-204440 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-204471 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom |
| R3-204472 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation, CATT, ZTE, Huawei |
| R3-204473 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation, Ericsson, Huawei |
| R3-204474 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, CATT, Huawei |
| R3-204492 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-204493 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-204509 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-204510 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| 15.2.1.1 | S1/NG Issues | |
| R3-203277 | (TP for NR_Mob_enh BL CR for TS 38.413): Consideration on the fallback indication | Nokia, Nokia Shanghai Bell |
| R3-203279 | (TP for LTE_feMob BL CR for TS 36.413): Consideration on the fallback indication | Nokia, Nokia Shanghai Bell |
| R3-203331 | (TP for NR_Mob_enh-Core BL CR for TS 38.413) AMF capability indication in NG based DAPS handover | Qualcomm Incorporated |
| R3-203332 | (TP for LTE_feMob-Core BL CR for TS 36.413) MME capability indication in S1 based DAPS handover | Qualcomm Incorporated |
| R3-203508 | (TP for NR_Mob_enh BL CR for TS 38.413): Left issues for S1/NG DAPS handover | Huawei |
| R3-203509 | (TP for LTE_feMob-Core BL CR for TS 36.413): Left issues for S1/NG DAPS handover | Huawei |
| R3-203564 | (TP for [LTE_feMob] BL CR for TS 36413)Remaining S1 Issues for DAPS HO | CATT |
| R3-203565 | (TP for [NR_Mob_enh] BL CR for TS 38413)Remaining NG Issues for DAPS HO | CATT |
| R3-203786 | Support of S1 and NG DAPS HO | Ericsson |
| R3-203787 | (TP for LTE_feMob BL CR for TS 36.413): Support of S1 DAPS HO | Ericsson |
| R3-203788 | (TP for NR Mob BL CR for TS 38.413): Support of NG DAPS HO | Ericsson |
| R3-203924 | (TP for LTE_feMob BL CR for TS 36.413) DAPS Response Information per E-RAB for S1 | Samsung |
| R3-203925 | (TP for NR_Mob_enh BL CR for TS 38.413) DAPS Response Information per DRB for NG | Samsung |
| R3-203983 | CB: # 33_MobEnh_DAPS_S1_NG - Summary of email discussion | Nokia - moderator |
| R3-204293 | (TP for NR_Mob_enh BL CR for TS 38.423) Change of the name of the Early Forwarding Transfer procedure | Nokia |
| R3-204294 | (TP for LTE_Mob_enh BL CR for TS 36.423) Change of the name of the Early Forwarding Transfer procedure | Nokia |
| R3-204296 | (TP for LTE_feMob BL CR for TS 36.413): Support of S1 DAPS HO | Ericsson |
| R3-204297 | (TP for NR Mob BL CR for TS 38.413): Support of NG DAPS HO | Ericsson |
| 15.2.1.2 | X2/Xn Issues | |
| R3-203187 | (TP for NR_Mob_enh BL CR for TS 38.423) Correction of DL Forwarding IE set to “DL forwarding proposed”for DAPS | ZTE |
| R3-203188 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Leftover Issues with DAPS Fallback to Rel-14 MBB | ZTE |
| R3-203191 | (TP for NR_Mob_enh BL CR for TS 38.423) Leftover Issues with DAPS Fallback to Rel-14 MBB | ZTE |
| R3-203276 | (TP for NR_Mob_enh BL CR for TS 38.423): Consideration on the fallback indication | Nokia, Nokia Shanghai Bell |
| R3-203278 | (TP for LTE_feMob BL CR for TS 36.423): Consideration on the fallback indication | Nokia, Nokia Shanghai Bell |
| R3-203326 | (TP for LTE_feMob-Core BL CR for TS 36.423) Remaining issues in DAPS handover over X2 | Qualcomm Incorporated |
| R3-203327 | (TP for NR_Mob_enh-Core BL CR for TS 38.423) Remaining issues in DAPS handover over Xn | Qualcomm Incorporated |
| R3-203505 | (TP for NR_Mob_enh BL CR for TS 38.423): Left issues for DAPS handover | Huawei |
| R3-203506 | (TP for LTE_feMob-Core BL CR for TS 36.423): Left issues for DAPS handover | Huawei |
| R3-203529 | (TP for NR_Mob_enh BL CR for TS 38.423) Introduce DAPS HO indicator and fallback mechanism for NR | China Telecom |
| R3-203530 | (TP for LTE_Mob_enh BL CR for TS 36.423) Introduce DAPS HO indicator and fallback mechanism for LTE- | China Telecom |
| R3-203566 | Remaining X2/Xn/E1 Issues for DAPS HO | CATT |
| R3-203567 | (TP for [LTE_feMob] BL CR for TS 36423)Remaining Issues for DAPS HO | CATT |
| R3-203568 | (TP for [NR_Mob_enh] BL CR for TS 38423)Remaining Issues for DAPS HO | CATT |
| R3-203764 | DAPS HO handling during preparation | Intel Corporation |
| R3-203765 | (TP for LTE_feMob-Core BL CR for TS 36.423): DAPS HO handling during preparation | Intel Corporation |
| R3-203766 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): DAPS HO handling during preparation | Intel Corporation |
| R3-203789 | DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-203790 | (TP for NR Mob BL CR for TS 38.423): DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-203791 | (TP for LTE_feMob BL CR for TS 36.423): DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-203918 | Remaining issues on DAPS handover | LG Electronics |
| R3-203926 | (TP for LTE_feMob BL CR for TS 36.423) DAPS Response Information per E-RAB for X2 | Samsung |
| R3-203927 | (TP for NR_Mob_enh BL CR for TS 38.423) DAPS Response Information per DRB for Xn | Samsung |
| R3-203984 | CB: # 34_MobEnh_DAPS_X2_Xn - Summary of email discussion | Ericsson - moderator |
| R3-204300 | (TP for LTE_feMob-Core BL CR for TS 36.423): DAPS HO handling during preparation | Intel Corporation |
| R3-204301 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): DAPS HO handling during preparation | Intel Corporation |
| 15.2.1.3 | RLC-UM Issues | |
| R3-203328 | (TP for LTE_feMob-Core BL CR for TS 36.300) PDCP SN continuity for RLC-UM bearer in DAPS HO | Qualcomm Incorporated |
| R3-203329 | (TP for NR_Mob_enh-Core BL CR for TS 38.300) PDCP SN continuity for RLC-UM bearer in DAPS HO | Qualcomm Incorporated |
| R3-203547 | (TP for LTE_feMob BL CR for TS 36.300) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung, Ericsson |
| R3-203548 | (TP for NR_Mob_enh BL CR for TS 38.300) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung, Ericsson |
| R3-203985 | CB: # 32_MobEnh_DAPS_RLC-UM - Summary of email discussion | Samsung - moderator |
| 15.2.3 | NR | |
| R3-203507 | Left issues for DAPS handover for E1 | Huawei |
| R3-203569 | CR to TS 38.463 for Remaining Issues for DAPS HO | CATT |
| R3-203767 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): DAPS HO handling during preparation | Intel Corporation |
| R3-203768 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): DAPS HO handling during preparation | Intel Corporation |
| R3-203769 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Correction for DAPS HO on inter-gNB-DU mobility scenarios | Intel Corporation |
| R3-203986 | CB: # 35_MobEnh_DAPS_E1 - Summary of email discussion | Intel - moderator |
| R3-204226 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): DAPS HO handling during preparation | Intel Corporation |
| R3-204227 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Correction for DAPS HO on inter-gNB-DU mobility scenarios | Intel Corporation |
| R3-204284 | TS38.460 E1 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-204332 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): DAPS HO handling during preparation | Intel Corporation |
| 15.3.1.1 | Conditional PSCell Change | |
| R3-203199 | Further Discussion of Coordination between CHO and CPC | ZTE |
| R3-203270 | Avoiding simultaneous CHO and CPC | Nokia, Nokia Shanghai Bell |
| R3-203271 | (TP for NR_Mob_enh BL CR for TS 38.423): A solution to enable the MN to block CPC usage | Nokia, Nokia Shanghai Bell |
| R3-203272 | (TP for LTE_feMob BL CR for TS 36.423): A solution to enable the MN to block CPC usage | Nokia, Nokia Shanghai Bell |
| R3-203273 | Response LS on avoiding simultaneous CHO and CPC | Nokia, Nokia Shanghai Bell |
| R3-203330 | Avoiding concurrent CHO and CPC | Qualcomm Incorporated |
| R3-203510 | (TP for NR_Mob_enh BL CR for TS 37.340): Stage 2 correction for CPC | Huawei |
| R3-203511 | (TP for NR_Mob_enh BL CR for TS 38.423): Avoidance of simultaneous CHO and CPC configuration | Huawei |
| R3-203512 | (TP for LTE_feMob BL CR for TS 36.423): Avoidance of simultaneous CHO and CPC configuration | Huawei |
| R3-203570 | Issue of Avoiding Simultaneous CHO and CPC | CATT |
| R3-203571 | (TP for [LTE_feMob] BL CR for TS 36423)Issue of Avoiding Simultaneous CHO and CPC | CATT |
| R3-203572 | (TP for [NR_Mob_enh] BL CR for TS 38423)Issue of Avoiding Simultaneous CHO and CPC | CATT |
| R3-203633 | (TP for NR_Mob_enh BL CR for TS 38.401) CPC Complete message correction | Google Inc. |
| R3-203634 | (TP for NR_Mob_enh BL CR for TS 38.423) Applicable architecture for CPC | Google Inc. |
| R3-203792 | Simultaneous CHO and CPC restriction | Ericsson |
| R3-203929 | Discussion on avoiding simultaneous CHO and CPC | Samsung |
| R3-203945 | Response to R3-203792 | Nokia, Nokia Shanghai Bell |
| R3-203987 | CB: # 36_MobEnh_CondPSCell_chg - Summary of email discussion | Samsung - moderator |
| R3-204176 | (TP for NR_Mob_enh BL CR for TS 38.401) CPC Complete message correction | Google Inc. |
| 15.3.1.2 | CHO Preparation | |
| R3-203793 | (TP for NR Mob BL CR for TS 38.423) CHO in MR-DC operation | Ericsson |
| R3-203794 | (TP for NR Mob BL CR for TS 37.340) CHO in MR-DC operation | Ericsson |
| R3-203988 | CB: # 37_MobEnh_CHOprep_MR-DC - Summary of email discussion | Ericsson - moderator |
| R3-204148 | (TP for NR Mob BL CR for TS 38.423) CHO in MR-DC operation | Ericsson |
| R3-204149 | (TP for NR Mob BL CR for TS 37.340) CHO in MR-DC operation | Ericsson |
| R3-204150 | (TP for LTE_feMob BL CR for TS 36.423) CHO in MR-DC operation | Ericsson |
| R3-204151 | (TP for LTE_feMob BL CR for TS 36.300) CHO in MR-DC Operation | Ericsson |
| 15.3.1.3 | CHO Modification | |
| R3-203200 | (TP for NR_Mob_enh BL CR for TS 38.473) Introduction of New Cause Value for gNB-DU Initiated CHO Modify&Re-setup | ZTE |
| R3-203201 | (TP for NR_Mob_enh BL CR for TS 38.463) Introduction of New Cause Value for gNB-CU-UP Initiated CHO Modify&Re-setup | ZTE |
| R3-203274 | (TP for NR_Mob_enh BL CR for TS 38.423): Completion of the work on the modification of a CHO | Nokia, Nokia Shanghai Bell |
| R3-203275 | (TP for LTE_feMob BL CR for TS 36.423): Completion of the work on the modification of a CHO | Nokia, Nokia Shanghai Bell |
| R3-203325 | (TP for NR_Mob_enh-Core BL CR for TS 38.423) Remaining issues in CHO modification | Qualcomm Incorporated |
| R3-203513 | (TP for NR_Mob_enh BL CR for TS 38.423): CHO Modification | Huawei |
| R3-203514 | (TP for LTE_feMob BL CR for TS 36.423): CHO Modification | Huawei |
| R3-203515 | (TP for NR_Mob_enh BL CR for TS 38.473): CHO Modification | Huawei |
| R3-203531 | Discussion on remaining issues for CHO Modification | China Telecom |
| R3-203532 | (TP for LTE_Mob_enh BL CR for TS 36.423) Target-initiated CHO Modification | China Telecom |
| R3-203533 | (TP for NR_Mob_enh BL CR for TS 38.423) Target-initiated CHO Modification | China Telecom |
| R3-203573 | Discussion on Remaining Issues of CHO Modification | CATT |
| R3-203574 | (TP for [LTE_feMob] BL CR for TS 36423)Remaining Issues of CHO Modification | CATT |
| R3-203575 | (TP for [NR_Mob_enh] BL CR for TS 38423)Remaining Issues of CHO Modification | CATT |
| R3-203795 | CHO - Modification from target node | Ericsson |
| R3-203989 | CB: # 38_MobEnh_CHOmod - Summary of email discussion | Huawei - moderator |
| R3-204184 | (TP for NR_Mob_enh BL CR for TS 38.423): CHO Modification | Huawei |
| R3-204185 | (TP for LTE_feMob BL CR for TS 36.423): CHO Modification | Huawei |
| R3-204186 | (TP for NR_Mob_enh BL CR for TS 38.473): CHO Modification | Huawei |
| R3-204233 | (TP for NR_Mob_enh BL CR for TS 38.473) Introduction of New Cause Value for gNB-DU Initiated CHO Modify&Re-setup | ZTE |
| 15.3.1.4 | CHO Cancellation | |
| R3-203723 | (TP for NR_Mob_enh BL CR for TS 38.423) Conditional HO Cancel procedure and HO Success procedure in 38.423 | NEC |
| R3-203724 | (TP for NR_Mob_enh BL CR for TS 36.423) Conditional HO Cancel procedure and HO Success procedure in 36.423 | NEC |
| R3-203990 | CB: # 39_MobEnh_CHOcancel - Summary of email discussion | NEC - moderator |
| R3-204163 | (TP for NR_Mob_enh BL CR for TS 38.423) Conditional HO Cancel procedure and HO Success procedure in 38.423 | NEC |
| R3-204164 | (TP for NR_Mob_enh BL CR for TS 36.423) Conditional HO Cancel procedure and HO Success procedure in 36.423 | NEC |
| 15.3.3 | NR | |
| R3-203202 | (TP for NR_Mob_enh BL CR for TS 38.473) Introduction of NR CGI IE into UL RRC MESSAGE TRANSFER Message | ZTE, CATT, Google, Qualcomm Incorporated, China Telecom, China Unicom |
| R3-203218 | (TP for NR_Mob_enh BL CR for TS 38.470) Introduction of Access Success Procedure | ZTE, Intel Corporation |
| R3-203219 | TS38.460 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-203589 | CHO in E1 interface | NEC |
| R3-203590 | CR to 38.463 for E1 impact on CHO | NEC |
| R3-203591 | (TP for NR_Mob_enh BL CR for TS 38.473) Introduce HO Success message in F1AP | NEC |
| R3-203635 | (TP for NR_Mob_enh BL CR for TS 38.401) Access success notification for Cell ID | Google Inc. |
| R3-203636 | (TP for NR_Mob_enh BL CR for TS 38.473) Access success notification for Cell ID | Google Inc. |
| R3-203770 | F1 needs a new class-2 message like HO SUCCESS | Intel Corporation, ZTE |
| R3-203771 | (TP for NR_Mob_enh-Core BL CR for TS 38.473): F1 needs a new class-2 message like HO SUCCESS | Intel Corporation, ZTE |
| R3-203772 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): F1 needs a new class-2 message like HO SUCCESS | Intel Corporation, ZTE |
| R3-203796 | DU Connection Success for CHO and CPC | Ericsson |
| R3-203797 | (TP for NR Mob BL CR for TS 38.473) DU Connection Success for CHO and CPC | Ericsson |
| R3-203892 | Discussion on E1 impact during Conditional Handover | CATT,CMCC |
| R3-203893 | CR to TS 38.463 for E1 impact during Conditional Handover | CATT,CMCC |
| R3-203991 | CB: # 41_MobEnh_CHO - Summary of email discussion | ZTE - moderator |
| R3-203992 | CB: # 42_MobEnh_CHO_E1 - Summary of email discussion | CATT - moderator |
| R3-204228 | (TP for NR_Mob_enh-Core BL CR for TS 38.473): F1 needs a new class-2 message like HO SUCCESS | Intel Corporation, ZTE, NEC |
| R3-204229 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): F1 needs a new class-2 message like HO SUCCESS | Intel Corporation, ZTE, NEC |
| R3-204231 | (TP for LTE_feMob_enh-Core BL CR for TS 36.423): HO SUCCESS alignment with F1 ACCESS SUCCESS | Intel |
| R3-204232 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): HO SUCCESS alignment with F1 ACCESS SUCCESS | Intel |
| R3-204283 | TS38.460 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom, Intel Corporation |
| R3-204285 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): CB: # 42_MobEnh_CHO_E1 | Intel |
| R3-204286 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): CB: # 42_MobEnh_CHO_E1 | Intel |
| R3-204333 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): CB: # 42_MobEnh_CHO_E1 | Intel |
| 15.4.1.1 | Handover Interruption Reduction | |
| R3-203800 | Early data forwarding and CU-UP DL transmission start/stop | Ericsson |
| R3-203801 | Early data forwarding and CU-UP DL transmission start/stop | Ericsson |
| 15.4.1.2 | CHO | |
| R3-203534 | Discussion on early data forwarding for Conditional Handover | China Telecom |
| R3-203535 | (TP for LTE_Mob_enh BL CR for TS 36.423) Introduce Early Forwarding Tranfer Request message for early data forwarding | China Telecom |
| R3-203536 | (TP for NR_Mob_enh BL CR for TS 38.423) Introduce Early Forwarding Tranfer Request message for early data forwarding | China Telecom |
| R3-203639 | (TP for NR_Mob_enh BL CR for TS 38.300): Data forwarding leftovers | Huawei |
| R3-203640 | (TP for LTE_feMob BL CR for TS 36.300): Data forwarding leftovers | Huawei |
| R3-203759 | (TP for NR_Mob_enh BL CR for TS 38.423): Early Data Forwarding for CHO | Apple Inc. |
| R3-203760 | (TP for LTE_feMob-Core BL CR for TS 36.423): Early Data Forwarding for CHO | Apple Inc. |
| R3-203773 | Full configuration CHO command indication | Intel Corporation |
| R3-203774 | (TP for LTE_feMob-Core BL CR for TS 36.423): Full configuration CHO command indication | Intel Corporation |
| R3-203775 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): Full configuration CHO command indication | Intel Corporation |
| R3-203894 | (TP for [LTE_feMob] BL CR for TS 36423)Early Data Forwarding for CHO | CATT |
| R3-203895 | (TP for [NR_Mob_enh] BL CR for TS 38423)Early Data Forwarding for CHO | CATT |
| R3-203993 | CB: # 44_MobEnh_EarlyDataFwd - Summary of email discussion | China Telecom - moderator |
| 15.4.3 | NR | |
| R3-203588 | Autonomous report for Discarding DL COUNT | NEC |
| R3-203776 | Early Forwarding support for DAPS/CHO over E1 | Intel Corporation, ZTE, Google, CATT, Huawei, Samsung, NEC, LGE |
| R3-203777 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support for DAPS/CHO over E1 | Intel Corporation, ZTE, Google, CATT, Huawei, Samsung, NEC, LGE |
| R3-203798 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-203799 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-203994 | CB: # 45_MobEnh_NR_EarlyDataFwd - Summary of email discussion | Intel - moderator |
| R3-204087 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-204230 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support for DAPS/CHO over E1 | Intel Corporation, ZTE, Google, CATT, Huawei, Samsung, NEC, LGE |
| R3-204329 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-204334 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support for DAPS/CHO over E1 | Intel Corporation, ZTE, Google, CATT, Huawei, Samsung, NEC, LGE |
| R3-204512 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, Intel Corporation, NEC, Huawei |
| 16.1 | General | |
| R3-203022 | CR to TS 38.460 on support of NPN | Huawei, China Telecom |
| R3-203024 | BL CR NPN for 38.401 | China Telecommunications |
| R3-203060 | Introduction of Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203061 | Introduction of Non-Public Networks | Qualcomm Incorporated |
| R3-203062 | Introduction of Non-Public Networks | Ericsson |
| R3-203063 | Introduction of Non-Public Networks for TS38.463 | ZTE |
| R3-203064 | CR to TS 38.470 on support of NPN | Huawei, China Telecom |
| R3-203065 | Introduction of NPN | Huawei, China Telecom |
| R3-203356 | (TP to BL CR#0290 / 38.413 on NPN) Removal of unused SNPN-ID in ASN.1 | Qualcomm Incorporated |
| R3-203406 | [TP for BL CR 38.423] Rapporteur’s Updates for XnAP NPN BL CR | Ericsson |
| R3-203453 | Information on draft 38.300 RAN2 NPN Baseline CR | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-203538 | Updated work plan for PRN WI | China Telecom |
| R3-203995 | CB: # 18_NPN_BLs - Summary of email discussion | China Telecom - moderator |
| R3-204422 | CR to TS 38.460 on support of NPN | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204424 | BL CR NPN for 38.401 | China Telecom, Nokia, Nokia Shanghai Bell, Huawei |
| R3-204455 | Introduction of Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-204456 | Introduction of Non-Public Networks | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, ZTE |
| R3-204457 | Introduction of Non-Public Networks | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, ZTE |
| R3-204458 | Introduction of Non-Public Networks for TS38.463 | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, China Telecom |
| R3-204459 | CR to TS 38.470 on support of NPN | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-204460 | Introduction of NPN | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-204513 | BL CR NPN for TS 38.401 | China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| 16.2 | Stage 2 Aspects | |
| R3-203407 | [TP for NPN BL CR 38.300] Further proposals for NPN BL CR for 38.300 | Ericsson |
| R3-203408 | [TP for NPN BL CR 38.401] Further proposals for NPN BL CR for 38.401 | Ericsson |
| R3-203454 | (TP for NPN BL CR for 38.300) Correction of NPN Mobility in Inactive State | Nokia, Nokia Shanghai Bell |
| R3-203455 | (TP for NPN BL CR for 38.300) Correction of NPN Paging | Nokia, Nokia Shanghai Bell |
| R3-203583 | (TP for NPN BL CR for TS 38.300): Paging Aspects for SNPN | NEC |
| R3-203627 | (TP to BL CR for 38.300 on NPN) Refining stage 2 of NPN | Qualcomm Incorporated |
| R3-203631 | TP for NPN BL CR for 38.401 | China Telecommunications |
| R3-203708 | (TP for NPN BL CR for TS 38.300): Stage 2 aspects for NPN | Huawei |
| R3-203709 | (TP for NPN BL CR for TS 38.401): RAN sharing with SNPN over F1 | Huawei |
| R3-203996 | CB: # 19_NPN_st2 - Summary of email discussion | Huawei - moderator |
| R3-204124 | (TP for NPN BL CR for 38.300) Correction of NPN Paging | Nokia, Nokia Shanghai Bell, NEC |
| R3-204143 | (TP for NPN BL CR for TS 38.300): Stage 2 aspects for NPN | Huawei |
| R3-204155 | (TP to BL CR for 38.300 on NPN) Refining stage 2 of NPN | Qualcomm Incorporated |
| R3-204156 | [TP for NPN BL CR 38.300] Further proposals for NPN BL CR for 38.300 | Ericsson |
| R3-204265 | TP for NPN BL CR for 38.401 | China Telecommunications |
| 16.3 | NG Aspects | |
| R3-203262 | Discussion on NPN Mobility Information | ZTE Corporation |
| R3-203263 | Update on NPN UE mobility information for TS38.413 | ZTE Corporation |
| R3-203409 | How to deal with 23.502 specification on UE Configuration Update procedure in NGAP | Ericsson, NTT DoCoMo |
| R3-203410 | LS on NG-RAN behaviour upon AMF triggered changes of the MRL for PNI-NPN | Ericsson, NTT DoCoMo |
| R3-203411 | [TP for BL CR 38.413] Finalisation of work on NGAP for NPN | Ericsson |
| R3-203456 | (TP for NPN BL CR for 38.413) Correction of NPN Access Information | Nokia, Nokia Shanghai Bell |
| R3-203457 | (TP for NPN BL CR for 38.413) Correction of NPN Access Cause value | Nokia, Nokia Shanghai Bell |
| R3-203539 | On signalling CAG support information over NG | China Telecom |
| R3-203582 | (TP for NPN BL CR for TS 38.413) Remaining issue on MRL in NPN | NEC |
| R3-203710 | (TP for NPN BL CR for TS 38.413): Cause value and configuration aspects for NPN | Huawei |
| R3-203711 | (TP for NPN BL CR for TS 38.413): Mobility related aspects for NPN | Huawei |
| R3-203919 | (TP for NPN BL CR for TS 38.413): Remaining issues on NGAP for NPN | LG Electronics |
| R3-203920 | [Draft] LS on registration area allocation for CAG-only UEs | LG Electronics |
| R3-203997 | CB: # 20_NPN_NG - Summary of email discussion | Ericsson - moderator |
| R3-204157 | LS on NG-RAN behaviour upon AMF triggered changes of the MRL for PNI-NPN | Ericsson, NTT DoCoMo |
| R3-204324 | LS on NG-RAN behaviour upon AMF triggered changes of the MRL for PNI-NPN | Ericsson, NTT DoCoMo |
| 16.4 | Xn Aspects | |
| R3-203264 | Update on NPN UE mobility information for TS38.423 | ZTE Corporation |
| R3-203412 | [TP for BL CR 38.423] Finalisation of work on XnAP for NPN | Ericsson |
| R3-203458 | (TP for NPN BL CR for 38.423) Correction of NPN Support Information | Nokia, Nokia Shanghai Bell |
| R3-203459 | (TP for NPN BL CR for 38.423) Correction of NPN Mobility cause value | Nokia, Nokia Shanghai Bell |
| R3-203684 | Discussion on RAN sharing in XN interface | CATT |
| R3-203685 | (TP on NPN BLCR for 38.423) Correction on RAN sharing in XN interface | CATT |
| R3-203712 | (TP for NPN BL CR for TS 38.423): Mobility related aspects for NPN | Huawei |
| R3-203713 | (TP for NPN BL CR for TS 38.423): RAN sharing with NPN over Xn | Huawei |
| R3-203998 | CB: # 21_NPN_Xn - Summary of email discussion | Nokia - moderator |
| R3-204144 | (TP for NPN BL CR for TS 38.423): Mobility related aspects for NPN | Huawei |
| R3-204145 | (TP for NPN BL CR for TS 38.423): RAN sharing with NPN over Xn | Huawei |
| R3-204158 | [TP for BL CR 38.423] Finalisation of work on XnAP for NPN | Ericsson |
| 16.5 | F1 Aspects | |
| R3-203127 | (TP for NPN BL CR for TS 38.473): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-203129 | (TP for NPN BL CR for TS 38.470): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-203265 | Open issues of NPN on F1 | ZTE Corporation |
| R3-203266 | TP for NPN support to TS38.473 | ZTE Corporation |
| R3-203413 | [TP for BL CR 38.473] Finalisation of work on F1AP for NPN | Ericsson |
| R3-203430 | [TP for BL CR 38.470] Finalisation of work on TS 38.470 for NPN | Ericsson |
| R3-203537 | TP for NPN BL CR for 38.401 | China Telecom, Ericsson, Huawei |
| R3-203683 | Discussion on F1 open issue | CATT |
| R3-203714 | (TP for NPN BL CR for TS 38.470): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-203715 | (TP for NPN BL CR for TS 38.473): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-203999 | CB: # 22_NPN_F1 - Summary of email discussion | Huawei - moderator |
| R3-204188 | (TP for NPN BL CR for TS 38.470): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-204189 | (TP for NPN BL CR for TS 38.473): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-204400 | (TP for NPN BL CR for TS 38.470): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-204401 | (TP for NPN BL CR for TS 38.473): Further support of NPN over F1 | Huawei, China Telecommunication |
| 16.6 | E1 Aspects | |
| R3-203131 | (TP for NPN BL CR for TS 38.463): NPN for E1 | Nokia, Nokia Shanghai Bell |
| R3-203132 | (TP for NPN BL CR for TS 38.460): NPN for E1 | Nokia, Nokia Shanghai Bell |
| R3-203268 | Open issues of NPN on E1 | ZTE Corporation |
| R3-203269 | TP for NPN support to TS38.463 | ZTE Corporation |
| R3-203414 | Finalisation of work on E1AP for NPN | Ericsson |
| R3-203716 | (TP for NPN BL CR for TS 38.460): Further support of NPN over E1 | Huawei, China Telecommunication |
| R3-203717 | (TP for NPN BL CR for TS 38.463): Further support of NPN over E1 | Huawei, China Telecommunication |
| R3-204000 | CB: # 23_NPN_E1 - Summary of email discussion | Ericsson - moderator |
| R3-204292 | (TP for NPN BL CR for TS 38.463): NPN for E1 | Nokia, Nokia Shanghai Bell |
| R3-204309 | (TP for NPN BL CR for TS 38.463): Further support of NPN over E1 | Huawei, China Telecommunication |
| 17.1 | General | |
| R3-203011 | Introduction of NR_IIOT support to TS 38.415 | Nokia, Nokia Shanghai Bell |
| R3-203072 | NRIIOT Higher Layer Multi-Connectivity | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-203073 | Introduction of NR_IIOT support to TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei |
| R3-203074 | Introduction of NR_IIOT support to TS 38.423 | Ericsson |
| R3-203075 | Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC, Ericsson |
| R3-203076 | Introduction of NR_IIOT support to TS 38.463 | ZTE |
| R3-203077 | Introduction of NR_IIOT support to TS 38.473 | Huawei |
| R3-203718 | (TP for NR_IIOT BL CR for TS 38.473): Proposed rapporteur changes to the BL CR | Huawei |
| R3-204001 | CB: # NRIIOT1-BLs - Summary of email discussion | Nokia - moderator |
| R3-204049 | Introduction of NR_IIOT support to TS 38.423 | Ericsson |
| R3-204071 | Introduction of NR_IIOT support to TS 38.463 | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT |
| R3-204127 | (TP for NR_IIOT BL CR for TS 38.473): Proposed rapporteur changes to the BL CR | Huawei |
| R3-204411 | Introduction of NR_IIOT support to TS 38.415 | Nokia, Nokia Shanghai Bell |
| R3-204467 | NRIIOT Higher Layer Multi-Connectivity | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-204468 | Introduction of NR_IIOT support to TS 38.413 | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Samsung, ZTE |
| R3-204469 | Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC, Ericsson, CATT, Samsung, Nokia, Nokia Shanghai Bell |
| R3-204470 | Introduction of NR_IIOT support to TS 38.473 | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT, Samsung |
| R3-204503 | Introduction of NR_IIOT support to TS 38.423 | Ericsson, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT |
| R3-204504 | Introduction of NR_IIOT support to TS 38.463 | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung |
| 17.2.1 | PDCP Duplication for CA-only and for NR DC with CA | |
| R3-203652 | PDCP duplication with more than 2 entities for F1 stage 2 (including E1 stage 2) | Huawei |
| R3-204002 | CB: # NRIIOT2-PDCPdup_morethan2 - Summary of email discussion | Huawei - moderator |
| R3-204076 | PDCP duplication with more than 2 entities for F1 stage 2 (including E1 stage 2) | Huawei |
| R3-204077 | PDCP duplication with more than 2 entities for E1 stage 2 | Huawei |
| R3-204505 | PDCP duplication with more than 2 entities for F1 stage 2 | Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell |
| R3-204506 | PDCP duplication with more than 2 entities for E1 stage 2 | Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell |
| 17.2.2 | Dynamic Control | |
| R3-203174 | Consideration on UL PDCP duplication | ZTE |
| R3-203175 | (TP for Introduction of NR_IIOT support to TS 38.423) Initial UL duplication configuration | ZTE |
| R3-203176 | (TP for Introduction of NR_IIOT support to TS 38.473) Initial UL duplication configuration | ZTE |
| R3-203177 | (TP for Introduction of NR_IIOT support to TS 38.425) UL PDCP duplication | ZTE |
| R3-203178 | (TP for Introduction of NR_IIOT support to TS 38.425) Open issues on DL PDCP duplication | ZTE |
| R3-203280 | Coordination of UL and DL transmission for multiplication over up to 4 RLCs | Nokia, Nokia Shanghai Bell |
| R3-203281 | (TPs for NR_IIoT BL CRs for TS 38.423): Enabling coordination for DL and UL multiplication over up to 4 RLCs | Nokia, Nokia Shanghai Bell |
| R3-203282 | (TPs for NR_IIoT BL CRs for TS 38.425): Enabling assistance information for DL coordination of the multiplication over up to 4 RLCs | Nokia, Nokia Shanghai Bell |
| R3-203283 | Response LS on Network Coordination for UL PDCP Duplication | Nokia, Nokia Shanghai Bell |
| R3-203415 | Remaining issues on Dynamic Control | Ericsson |
| R3-203576 | Discussion on Dynamic control of PDCP Duplication | CATT |
| R3-203577 | (TP for [NR_IIOT] BL CR for TS 38.425)Dynamic control of PDCP Duplication | CATT |
| R3-203653 | (TP for NR_IIOT BL CR for TS 38.423): PDCP duplication with more than 2 entities | Huawei |
| R3-203654 | (TP for NR_IIOT BL CR for TS 38.473): PDCP duplication with more than 2 entities | Huawei |
| R3-203655 | (TP for NR_IIOT BL CR for TS 38.425): Assistance information for DL PDCP duplication with more than 2 entities | Huawei, CMCC |
| R3-203656 | (TP for NR_IIOT BL CR for TS 38.425): Dynamic control of UL duplication | Huawei |
| R3-203657 | [DRAFT] Reply LS on coordination for UL duplication | Huawei |
| R3-203901 | Remaining issues of dynamic control | CMCC |
| R3-204003 | CB: # NRIIOT3-ULPDCPdup_ctrl - Summary of email discussion | CATT - moderator |
| R3-204168 | Response LS on Network Coordination for UL PDCP Duplication | Nokia, Nokia Shanghai Bell |
| R3-204180 | CB: # NRIIOT3-ULPDCPdup_ctrl - Summary of email discussion | CATT - moderator |
| R3-204181 | (TP for Introduction of NR_IIOT support to TS 38.423) Initial UL duplication configuration | ZTE |
| R3-204182 | (TP for NR_IIOT BL CR for TS 38.473): PDCP duplication with more than 2 entities | Huawei |
| R3-204183 | (TP for [NR_IIOT] BL CR for TS 38.425)Dynamic control of PDCP Duplication | CATT |
| 17.2.3 | Enhancements for More Efficient DL PDCP Duplication | |
| R3-203658 | (TP for NR_IIoT BL CR for TS 38.425): Finalization of enhancement 3 | Huawei |
| R3-204004 | CB: # NRIIOT4-PDCPdup_enh - Summary of email discussion | Huawei - moderator |
| 17.2.4.2 | Solution #1 | |
| R3-203170 | Discussion on the remaining issues of solution1 | ZTE |
| R3-203171 | (TP for Introduction of NR_IIOT support to TS38.413): Remaining issues of sol1 | ZTE |
| R3-203172 | (TP for Introduction of NR_IIOT support to TS38.423): Remaining issues of sol1 | ZTE |
| R3-203173 | (TP for Introduction of NR_IIOT support to TS38.463): Remaining issues of sol1 | ZTE |
| R3-203416 | Remaining issues on Higher Layer Multi-Connectivity | Ericsson |
| R3-203417 | Refining the Used RSN Information over NGAP | Ericsson |
| R3-203418 | Refining the Used RSN Information over XnAP | Ericsson |
| R3-203419 | Refining the SN Node ID sent to 5GC | Ericsson |
| R3-203420 | RSN related over E1AP | Ericsson |
| R3-203460 | (TP for BL CR NR IIoT for 38.413) Correction of used RSN | Nokia, Nokia Shanghai Bell |
| R3-203461 | (TP for BL CR NR IIoT for 38.423) Correction of used RSN | Nokia, Nokia Shanghai Bell |
| R3-203462 | (TP for BL CR NR IIoT for 38.463) Correction of Used RSN | Nokia, Nokia Shanghai Bell |
| R3-203578 | Remaining issues of the Solution#1 | CATT |
| R3-203579 | (TP for [NR_IIOT] BL CR for TS 38.413)Remaining issues of the Solution#1 | CATT |
| R3-203580 | (TP for [NR_IIOT] BL CR for TS 38.423)Remaining issues of the Solution#1 | CATT |
| R3-203581 | (TP for [NR_IIOT] BL CR for TS 38.463)Remaining issues of the Solution#1 | CATT |
| R3-203621 | (TP for NR_IIOT BL CR for TS 38.413) Redundant PDU session setup | Samsung |
| R3-203622 | (TP for NR_IIOT BL CR for TS 38.423) Redundant PDU session setup | Samsung |
| R3-203659 | (TP for NR_IIOT BL CR for TS 38.423): Higher layer duplication for solution 1 | Huawei |
| R3-203660 | (TP for NR_IIOT BL CR for TS 38.413): Higher layer duplication for solution 1 | Huawei |
| R3-203661 | (TP for NR_IIOT BL CR for TS 38.463): Higher layer duplication for solution 1 | Huawei |
| R3-203662 | (TP for NR_IIoT BL CR for TS 38.413) : Introducing updated QoS parameters in path switch request acknowledge | Huawei |
| R3-203911 | Discussion on open issues for Solution #1 | LG Electronics |
| R3-203912 | (TP for NR_IIOT BL CR for TS 38.413): Introduction of Redundant Transmission Information for Solution #1 | LG Electronics |
| R3-203913 | (TP for NR_IIOT BL CR for TS 38.423): Introduction of Redundant Transmission Information for Solution #1 | LG Electronics |
| R3-203914 | (TP for NR_IIOT BL CR for TS 38.463): Introduction of Redundant Transmission Information for Solution #1 | LG Electronics |
| R3-204005 | CB: # NRIIOT5-HLmulticonn_sol1 - Summary of email discussion | ZTE - moderator |
| R3-204048 | LS on QoS parameter update at Xn handover | Nokia |
| R3-204128 | (TP for NR_IIoT BL CR for TS 38.413) : Introducing updated QoS parameters in path switch request acknowledge | Huawei |
| R3-204132 | (TP for BL CR NR IIoT for 38.413) Correction of used RSN | Nokia, Nokia Shanghai Bell |
| R3-204133 | Refining the Used RSN Information over XnAP | Ericsson |
| R3-204134 | (TP for Introduction of NR_IIOT support to TS38.463): Remaining issues of sol1 | ZTE |
| R3-204203 | Refining the Used RSN Information over XnAP | Ericsson |
| R3-204302 | (TP for Introduction of NR_IIOT support to TS38.463): Remaining issues of sol1 | ZTE |
| R3-204307 | CB: # NRIIOT5-HLmulticonn_sol1 - Summary of email discussion | ZTE - moderator |
| R3-204325 | LS on QoS parameter update at Xn handover | Nokia |
| 17.3.3 | Time Reference Information | |
| R3-203663 | (TP for NR_IIOT BL CR for TS 38.473): Reference timing information | Huawei |
| R3-204006 | CB: # NRIIOT6-time_ref_info - Summary of email discussion | Huawei - moderator |
| 17.4 | Ethernet Type Bearer Signaling in NG-RAN | |
| R3-203032 | Support of Ethernet type | Nokia, Nokia Shanghai Bell |
| R3-203070 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-203071 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-203097 | Support of Ethernet Header Compression | Huawei, Samsung, CMCC, Nokia |
| R3-203098 | Support of Ethernet Header Compression | Huawei |
| R3-203421 | EHC updates on E1AP TP | Ericsson |
| R3-203463 | (TP for baseline CR478 Support of Ethernet Type Bearer for TS 38.463) Correction of Ethernet Compression | Nokia, Nokia Shanghai Bell |
| R3-204007 | CB: # NRIIOT7-Ethernet_Type_Bearer_Signaling - Summary of email discussion | Ericsson - moderator |
| R3-204142 | EHC updates on E1AP TP | Ericsson |
| R3-204430 | Support of Ethernet type | Nokia, Nokia Shanghai Bell, Huawei |
| R3-204465 | Support of Ethernet Type Bearer | Huawei, Vodafone, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-204466 | Support of Ethernet Type Bearer | Huawei, Vodafone, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-204490 | Support of Ethernet Header Compression | Huawei, Samsung, CMCC, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-204491 | Support of Ethernet Header Compression | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| 18.1 | General | |
| R3-203039 | Signalling UE capability Identity | Huawei |
| R3-203041 | Introducing Radio Capability Optimisation (RACS) | Nokia, Nokia Shanghai Bell |
| R3-203093 | Signalling UE capability Identity | Huawei, Samsung Electronics, CATT, Ericsson, Qualcomm |
| R3-203094 | X2AP support for Radio Capability Signaling Optimization | Samsung, CATT, Ericsson, Huawei, Qualcomm |
| R3-203095 | Introducing Radio Capability Optimisation (RACS) | Ericsson, Qualcomm, CATT, Samsung, Huawei |
| R3-203096 | Supporting of RACS in XnAP | CATT, Samsung, Huawei, Ericsson, Qualcomm |
| R3-203422 | [TP for BL CR 38.413] Rapporteurs update for NGAP RACS BL CR | Ericsson |
| R3-203522 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| R3-204008 | CB: # 16_RACS_BLs - Summary of email discussion | CATT - moderator |
| R3-204437 | Signalling UE capability Identity | Huawei |
| R3-204439 | Introducing Radio Capability Optimisation (RACS) | Nokia, Nokia Shanghai Bell |
| R3-204486 | Signalling UE capability Identity | Huawei, Samsung Electronics, CATT, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-204487 | X2AP support for Radio Capability Signaling Optimization | Samsung, CATT, Ericsson, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-204488 | Introducing Radio Capability Optimisation (RACS) | Ericsson, Qualcomm, CATT, Samsung, Huawei, Nokia, Nokia Shanghai Bell |
| R3-204489 | Supporting of RACS in XnAP | CATT, Samsung, Huawei, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| 18.2 | Open Items | |
| R3-203120 | Reply LS on RACS and signalling of UE capabilities at handover | 3GPP SA2 |
| R3-203122 | LS on different coding formats | 3GPP SA2 |
| R3-203220 | Further Discussion of RACS ID Usage in MR-DC Scenarios | ZTE |
| R3-203228 | TS37.340 Introduction of RACS Feature in MR-DC Rel-16 | ZTE, China Unicom |
| R3-203360 | Discussion on support of different coding formats | Ericsson |
| R3-203361 | [TP for NGAP BL CR for RACS] Support of different coding formats | Ericsson |
| R3-203362 | [TP for S1AP BL CR for RACS] Support of different coding formats | Ericsson |
| R3-203423 | Finalising work on RACS in RAN3 | Ericsson |
| R3-203424 | [TP for BL CR 36.423] On open topics for X2AP | Ericsson |
| R3-203425 | Introducing RACS | Ericsson |
| R3-203523 | Discussion on left issues for RACS | CATT |
| R3-203524 | Draft CR for 37.340 Supportingof RACS for EN-DC and MR-DC | CATT |
| R3-203549 | Supporting UE Radio Capability ID Mapping procedure in EN-DC | Samsung |
| R3-203550 | (TP for RACS for TS 36.423) Supporting UE Radio Capability ID Mapping procedure in EN-DC | Samsung |
| R3-203592 | (TP for RACS BL CR for TS 36.423) whether need of RACS function in MR-DC including EN-DC | NEC |
| R3-203593 | (TP for RACS BL CR for TS 38.423) whether need of RACS function in MR-DC including EN-DC | NEC |
| R3-203664 | (TP for RACS BL CR for TS 36.413): Signalling UE capability identity | Huawei |
| R3-203665 | (TP for RACS BL CR for TS 36.423): Signalling UE capability identity | Huawei |
| R3-203666 | (TP for RACS BL CR for TS 38.413): Signalling UE capability identity | Huawei |
| R3-203667 | Signalling UE capability identity for MR-DC | Huawei |
| R3-203668 | [Draft] LS reply on RACS multiple radio capability formats | Huawei |
| R3-203705 | (TP for NR BL CR for TS 36.413) Add the support for Mode of Operation A | Nokia, Nokia Shanghai Bell |
| R3-203706 | (TP for NR BL CR for TS 38.413) Add the support for Mode of Operation A | Nokia, Nokia Shanghai Bell |
| R3-204009 | CB: # 17_FolderName - Summary of email discussion | Huawei - moderator |
| R3-204141 | Draft CR for 37.340 Supportingof RACS for EN-DC and MR-DC | CATT, Huawei, ZTE |
| R3-204146 | (TP for RACS BL CR for TS 36.413): Signalling UE capability identity | Huawei |
| R3-204147 | LS reply on RACS multiple radio capability formats | Huawei |
| R3-204507 | Draft CR for 37.340 Supportingof RACS for EN-DC and MR-DC | CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| 19.1 | General | |
| R3-203031 | Positioning Support over F1AP CR | Huawei |
| R3-203082 | Introduction of NR Positioning in NRPPa | Ericsson, Intel |
| R3-203083 | Positioning support over F1AP | Huawei |
| R3-203084 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| R3-203102 | Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm |
| R3-203595 | (TP to BL CR for TS 38.470) FFS Removal | huawei |
| R3-203596 | (TP to BL CR for TS 38.305) Update on NG-RAN architecture with inclusion of missing BL CR | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-203597 | (TP to BL CR for TS 38.305) Clean up related CU-DU | Huawei |
| R3-203598 | Positioning support over F1AP | Huawei |
| R3-203733 | (TP to BL CR correction TP of TS 38.305): support of positioning over F1AP | Ericsson |
| R3-203734 | CR to TS 38.401 to add Reference for F1 support of positioning | Ericsson |
| R3-204010 | CB: # 24_Pos_BLs - Summary of email discussion | Intel - moderator |
| R3-204196 | (TP to BL CR for TS 38.470) FFS Removal | huawei |
| R3-204197 | (TP to BL CR for TS 38.305) Clean up related CU-DU | Huawei |
| R3-204198 | Positioning support over F1AP | Huawei |
| R3-204199 | (TP to BL CR for TS 38.305) Clean up related CU-DU with figure in 38.401 | Huawei |
| R3-204204 | (TP to BL CR for TS 38.305) Clean up related CU-DU | Huawei |
| R3-204475 | Introduction of NR Positioning in NRPPa | Ericsson, Intel |
| R3-204476 | Positioning support over F1AP | Huawei |
| R3-204477 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| R3-204494 | Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm |
| R3-204498 | Positioning support over F1AP | Huawei |
| 19.2.1 | NRPPa Impacts | |
| R3-204200 | (TP to BL CR for TS 38.455) Introduction Rx Beam Info Request | Huawei |
| R3-204208 | (TP to BL CR for TS 38.455) Introduction Rx Beam Info Request | Huawei |
| 19.2.1.1 | Common, TRP Issues | |
| R3-203115 | LS on NR Positioning gNB measurement report range and granularity | 3GPP RAN4 |
| R3-203431 | (TP for NR_POS BL CR for TS 38.455) Further details for the measurement procedures | Nokia, Nokia Shanghai Bell |
| R3-203432 | Update of the NRPPa Transport procedure to support NR positioning | Nokia, Nokia Shanghai Bell |
| R3-203599 | (TP to BL CR for TS 38.455/38.455) Measurment procedures & NRPP clean-up | Huawei |
| R3-203628 | (TP to BL CR#0008 / 38.455 on NR Positioning) Further considerations on NRPPa rel-16 | Qualcomm Incorporated |
| R3-203735 | Discussion on TRP ID issue in measurement messages | Ericsson, NTT DOCOMO Inc. |
| R3-203736 | (TP for NR_POS BL CR for TS 38.455) fixing TRP ID presence in positioning measurement messages | Ericsson, NTT DOCOMO Inc. |
| R3-204011 | CB: # 25_Pos_common_TRPs - Summary of email discussion | Ericsson - moderator |
| R3-204206 | CB: # 25_Pos_common_TRPs - Summary of email discussion | Ericsson - moderator |
| R3-204207 | (TP to BL CR#0008 / 38.455 on NR Positioning) Further considerations on NRPPa rel-16 | Qualcomm Incorporated |
| R3-204317 | (TP for NR_POS BL CR for TS 38.455) fixing TRP ID presence in positioning measurement messages | Ericsson, NTT DOCOMO Inc. |
| R3-204331 | (TP for NR_POS BL CR for TS 38.455) fixing TRP ID presence in positioning measurement messages | Ericsson, NTT DOCOMO Inc., Nokia, Nokia Shanghai Bell |
| R3-204335 | CB: # 25_Pos_common_TRPs - Summary of email discussion | Ericsson - moderator |
| R3-204497 | Update of the NRPPa Transport procedure to support NR positioning | Nokia, Nokia Shanghai Bell |
| 19.2.1.2 | NR E-CID | |
| R3-203433 | (TP for NR_POS BL CR for TS 38.455) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell |
| R3-203601 | (TP to BL CR for TS 38.455) NR E-CID measuremnt procedure | Huawei |
| R3-203740 | Reporting of SFTD measurements in NRPPa | Ericsson |
| R3-204012 | CB: # 26_Pos_NR_E-CID - Summary of email discussion | Nokia - moderator |
| R3-204130 | (TP for NR_POS BL CR for TS 38.305) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell |
| R3-204131 | (TP for NR_POS BL CR for TS 38.455) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Huawei |
| R3-204209 | CB: # 26_Pos_NR_E-CID - Summary of email discussion | Nokia - moderator |
| R3-204210 | (TP for NR_POS BL CR for TS 38.305) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell |
| R3-204211 | (TP for NR_POS BL CR for TS 38.455) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Huawei |
| R3-204272 | Reporting of SFTD measurements in NRPPa | Ericsson |
| 19.2.1.3 | Signaling Support for SRS and SSB Configuration | |
| R3-203103 | LS on UL RTOA reference time | 3GPP RAN1 |
| R3-203311 | [DRAFT] Reply LS on Aperiodic SRS | Intel Corporation |
| R3-203312 | (TP for NR_POS BL CR for TS 38.455) Aperiodic and SP SRS activation/triggering | Intel Corporation |
| R3-203313 | (TP for NR_POS BL CR for TS 38.305) Aperiodic and SP SRS activation/triggering | Intel Corporation |
| R3-203600 | (TP to BL CR for TS 38.455) Open issues related to SRS configuration procedure | Huawei |
| R3-203630 | (TP to BL CR#0008 / 38.455 on NR Positioning) Addition of UL SRS Activation and Deactivation Procedures | Qualcomm Incorporated |
| R3-203737 | Discussion on support of Aperiodic positioning of SRS configuration and other aspects | Ericsson |
| R3-203738 | (TP to TS 38.455 BL CR): support of Aperiodic positioning of SRS configuration and other aspects | Ericsson |
| R3-203739 | LS Reply on UL RTOA reference time | Ericsson |
| R3-204013 | CB: # 27_Pos_SRS_SRB - Summary of email discussion | Intel - moderator |
| R3-204191 | (TP to TS 38.455 BL CR): support of Aperiodic positioning of SRS configuration and other aspects | Ericsson |
| R3-204192 | LS Reply on UL RTOA reference time | Ericsson |
| R3-204201 | (TP to BL CR for TS 38.455) Open issues related to SRS configuration procedure | Huawei |
| R3-204212 | (TP to TS 38.455 BL CR): support of Aperiodic positioning of SRS configuration and other aspects | Ericsson |
| R3-204213 | (TP to BL CR for TS 38.455) Open issues related to SRS configuration procedure | Huawei |
| R3-204214 | [DRAFT] Reply LS on Aperiodic SRS | Intel Corporation |
| R3-204215 | CB: # 27_Pos_SRS_SRB - Summary of email discussion | Intel - moderator |
| R3-204299 | (TP to BL CR#0008 / 38.455 on NR Positioning) Addition of UL SRS Activation and Deactivation Procedures | Qualcomm Incorporated |
| R3-204327 | LS Reply on UL RTOA reference time | Ericsson |
| R3-204361 | (TP to BL CR#0495 / 38.473 on NR Positioning) Addition of UL SRS Activation and Deactivation Procedures | Ericsson |
| R3-204379 | Reply LS on Aperiodic SRS | Intel Corporation |
| 19.3 | Transmission Measurement Function | |
| R3-203602 | (TP for BL CR for TS 38.455/TS 38.470): TRP Geographical Coordinates | Huawei, Deutsche Telekom, LGU+, BT, Orange |
| R3-204014 | CB: # 28_Pos_Trans_Meas_fn - Summary of email discussion | Huawei - moderator |
| R3-204170 | (TP for BL CR for TS 38.455/TS 38.470): TRP Geographical Coordinates | Huawei, Deutsche Telekom, LGU+, BT, Orange |
| R3-204216 | (TP for BL CR for TS 38.455): TRP Geographical Coordinates | Huawei, Deutsche Telekom, LGU+, BT, Orange |
| R3-204217 | CB: # 28_Pos_Trans_Meas_fn - Summary of email discussion | Huawei - moderator |
| R3-204312 | (TP for BL CR for TS 38.470): TRP Geographical Coordinates | Huawei, Deutsche Telekom, LGU+, BT, Orange |
| 19.4 | Broadcast Assistance Data Delivery | |
| R3-203357 | (TP for NR_POS BL CR for TS 38.455) Need for target cell in NRPPa Assistance Data Broadcast | Qualcomm Incorporated |
| R3-203603 | (TP to BL CR for TS 38.455) Removal of FFS in Metadata for areaScope | Huawei |
| R3-203604 | (TP to BL CR for TS 38.473) Control and feedback procedure for Assistant information | huawei |
| R3-203741 | Addressing remaining issues of delivery of Positioning Assistance Data over F1AP | Ericsson |
| R3-203742 | (TP to F1AP BL CR): Addressing remaining issues of delivery of Positioning Assistance Data over F1AP | Ericsson |
| R3-203896 | Discussion on Positioning SI Area ID | CATT |
| R3-203897 | (TP for [NR_POS-Core] BL CR for TS 38.455) Discussion on Positioning SI Area ID | CATT |
| R3-204015 | CB: # 29_Pos_Broadcast_assist_data - Summary of email discussion | Huawei - moderator |
| R3-204218 | (TP for NR_POS BL CR for TS 38.455) Need for target cell in NRPPa Assistance Data Broadcast | Qualcomm Incorporated |
| R3-204219 | CB: # 29_Pos_Broadcast_assist_data - Summary of email discussion | Huawei - moderator |
| R3-204220 | (TP to F1AP BL CR): Addressing remaining issues of delivery of Positioning Assistance Data over F1AP | Ericsson |
| R3-204221 | [Draft] LS on mapping of PosSIB(s) to Area(s) | Huawei |
| R3-204380 | LS on mapping of PosSIB(s) to Area(s) | Huawei |
| 19.5 | Positioning Support in split gNB Architecture | |
| R3-203314 | (TP for NR_POS BL CR for TS 38.743) Aperiodic and SP SRS activation/triggering | Intel Corporation |
| R3-203605 | (TP to BL CR for TS 38.473) Completion of positioning function at F1AP | Huawei |
| R3-203629 | F1AP Transparent Support of NRPPa IEs | Qualcomm Incorporated |
| R3-203743 | Discussion on F1AP alignment issues and support of Aperiodic positioning of SRS configuration in NG-RAN | Ericsson |
| R3-203744 | (TP to F1AP BL CR 38.473): support of SRS positioning configuration over F1AP | Ericsson |
| R3-203758 | F1AP open issues for NR positioning | Nokia, Nokia Shanghai Bell |
| R3-204016 | CB: # 30_Pos_CU-DU_split - Summary of email discussion | Ericsson - moderator |
| R3-204190 | (TP to F1AP BL CR 38.473): support of SRS positioning configuration over F1AP | Ericsson |
| R3-204222 | Discussion on F1AP alignment issues and support of Aperiodic positioning of SRS configuration in NG-RAN | Ericsson |
| R3-204223 | (TP to BL CR for TS 38.473) Completion of positioning function at F1AP | Huawei, Ericsson |
| R3-204224 | CB: # 30_Pos_CU-DU_split - Summary of email discussion | Ericsson - moderator |
| 20.1 | General | |
| R3-203038 | Support of NR V2X over S1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-203040 | Support of NR V2X over NG | LG Electronics, Ericsson, Huawei, CATT |
| R3-203043 | Support of NR V2X SIB in gNB-DU | Ericsson |
| R3-203044 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics |
| R3-203045 | Support of NR V2X over Xn | Ericsson, LG Electronics, CATT, Huawei |
| R3-203046 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-203557 | (TP for TR 37.985) Updates of RAN3 progress on V2X | Huawei |
| R3-204017 | CB: # 1100_Email_V2X_BL_CRs - Summary of email discussion | Huawei - moderator |
| R3-204116 | (TP for TR 37.985) Updates of RAN3 progress on V2X | Huawei |
| R3-204120 | (TP for TR 37.985) Updates of RAN3 progress on V2X | Huawei |
| R3-204263 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-204436 | Support of NR V2X over S1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-204438 | Support of NR V2X over NG | LG Electronics, Ericsson, Huawei, CATT, Nokia, Nokia Shanghai Bell |
| R3-204441 | Support of NR V2X SIB in gNB-DU | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-204442 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-204443 | Support of NR V2X over Xn | Ericsson, LG Electronics, CATT, Huawei, Nokia, Nokia Shanghai Bell |
| R3-204511 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| 20.2.2 | V2X Support over F1 | |
| R3-203157 | Discussion on remaining issues on F1 | ZTE, Sanechips |
| R3-203239 | Remaining issues on F1 support for 5G sidelink resource modes | LG Electronics |
| R3-203240 | (TP for BLCR 38.473) remaining Issues on F1 | LG Electronics |
| R3-203470 | (TP for V2X BL CR for 38.473)SL DRB QoS | Intel Deutschland GmbH |
| R3-203520 | Further consideration on PC5 QoS Parameters over F1 | CATT |
| R3-203521 | (TP for NR BL CR for TS 38.473) PC5 QoS Parameters over F1 | CATT |
| R3-203558 | (TP for V2X BL CR for TS 38.473) F1 impacts for V2X | Huawei |
| R3-203559 | (TP for V2X BL CR for TS 38.473) New reference in DU to CU RRC Info | Huawei |
| R3-203707 | (TP for Support of NR V2X SIB in gNB-DU) Misc corrections for TS38.470 | Nokia, Nokia Shanghai Bell |
| R3-204018 | CB: # 1101_Email_V2X_F1 - Summary of email discussion | LG - moderator |
| R3-204268 | (TP for BLCR 38.473) remaining Issues on F1 | LG Electronics |
| R3-204351 | (TP for BLCR 38.473) remaining Issues on F1 | LG Electronics |
| 20.2.4 | Support for QoS | |
| R3-203464 | Support for Alternative QoS Profiles | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LGE, InterDigital, NTT Docomo INC. |
| R3-203465 | (TP for BL CR V2X for 38.413) Support for alternative QoS Profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LGE, InterDigital, NTT Docomo INC. |
| R3-203466 | Support for Alternative QoS Profiles | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LGE, InterDigital, NTT Docomo INC. |
| R3-203467 | Support for Alternative QoS Profiles | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LGE, InterDigital, NTT Docomo INC. |
| R3-203638 | Support of Alternative QoS Profiles | Huawei, Vodafone |
| R3-203745 | (TP to V2X BL CR for TS 38.423): Support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-203746 | (TP to V2X BL CR for TS 38.473): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-203747 | (TP to V2X BL CR for TS 38.470): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-203748 | Introducing alternative QoS profiles to E1AP | Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, InterDigital, NTT DOCOMO INC. |
| R3-203751 | (TP for BL CR V2X for 38.413) Support for alternative QoS profiles over NG | Vodafone |
| R3-203949 | Response to R3-203751 | Nokia, Nokia Shanghai Bell |
| R3-204019 | CB: # 1102_Email_V2X_QoS - Summary of email discussion | Nokia - moderator |
| R3-204047 | (TP for BL CR V2X for 38.413) Support for alternative QoS Profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LGE, InterDigital, NTT Docomo INC. |
| R3-204171 | Support for Alternative QoS profiles over E1 | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-204193 | (TP to V2X BL CR for TS 38.423): Support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-204194 | (TP to V2X BL CR for TS 38.473): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-204195 | (TP to V2X BL CR for TS 38.470): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-204499 | Introducing alternative QoS profiles to E1AP | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC. |
| R3-204508 | Support for Alternative QoS Profiles | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LGE, InterDigital, NTT Docomo INC. |
| 21.1 | General | |
| R3-203047 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom, Nokia, Nokia Shanghai Bell |
| R3-203048 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom, Nokia, Nokia Shanghai Bell |
| R3-203645 | Updated work plan for WWC | Huawei |
| R3-203646 | (TP for WWC BL CR for TS 29.413) Proposed rapporteur changes to the BL CR | Huawei |
| R3-204020 | CB: # 14_WWC_BLs - Summary of email discussion | Huawei - moderator |
| R3-204444 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom, Nokia, Nokia Shanghai Bell |
| R3-204445 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom, Nokia, Nokia Shanghai Bell |
| 21.2 | NG Support for WWC | |
| R3-203358 | [TP for BL CR NGAP] Selected PLMN ID in Initial UE Message for trusted non-3GPP access | Ericsson |
| R3-203647 | (TP for WWC BL CR for TS 29.413): Support for interfacing wireline and trusted non-3GPP access to the 5GC | Huawei, Telecom Italia, BT, Broadcom,Nokia , Nokia Shanghai Bell |
| R3-203648 | (TP for WWC BL CR for TS 38.413):Support for interfacing wireline and trusted non-3GPP access to the 5GC | Huawei, Telecom Italia, BT, Broadcom,Nokia , Nokia Shanghai Bell |
| R3-204021 | CB: # 15_WWC_NGAP - Summary of email discussion | Huawei - moderator |
| R3-204103 | (TP for WWC BL CR for TS 29.413): Support for interfacing wireline and trusted non-3GPP access to the 5GC | Huawei, Telecom Italia, BT, Broadcom,Nokia , Nokia Shanghai Bell |
| R3-204104 | (TP for WWC BL CR for TS 38.413):Support for interfacing wireline and trusted non-3GPP access to the 5GC | Huawei, Telecom Italia, BT, Broadcom,Nokia , Nokia Shanghai Bell |
| 31.2 | LTE | |
| R3-203749 | Reporting of per beam measurements and SFTD for E-CID inter-RAT results in LPPa | Ericsson, NTT DOCOMO Inc. |
| R3-203750 | Reporting of per beam measurements and SFTD inter-RAT results in LPPa | Ericsson, NTT DOCOMO Inc. |
| R3-203917 | Support beam level inter-RAT measurement report in E-CID measurement in LPPa | NTT DOCOMO, INC. |
| R3-204271 | Reporting of per beam measurements and SFTD inter-RAT results in LPPa | Ericsson, NTT DOCOMO Inc. |
| 31.3.3 | Direct Data Forwarding Between NG-RAN and E-UTRAN | |
| R3-203229 | Proceeding of 5G Intra-System Direct DF with Shared Source NG-RAN Node (R3-201646) | ZTE |
| R3-203230 | [Draft] LS about 5G Intra-system Various HO Scenarios Involving MR-DC | ZTE |
| R3-203241 | TS38.423 Support of 5G Intra-System Direct DF with Shared Source NG-RAN Node | ZTE, CATT, China Telecom, China Unicom |
| R3-203468 | Support of Direct Data Forwarding for Inter-System Handover | Nokia, Nokia Shanghai Bell, CATT, China Telecom, ZTE |
| R3-203469 | Correction of User Plane Inter-System Direct Forwarding | Nokia, Nokia Shanghai Bell |
| R3-203480 | Support of direct data forwarding for inter-system HO | China Telecom, CATT,Nokia , Nokia Shanghai Bell, ZTE |
| R3-203623 | Direct data forwarding for Inter-system HO in CP-UP seperation | Samsung |
| R3-203624 | Support direct data forwarding for inter-system handover | Samsung |
| R3-203650 | Direct data forwarding for inter-system handover over E1 | Huawei |
| R3-203651 | Direct data forwarding for inter-system handover over E1 | Huawei |
| R3-203697 | Discussion on E1AP for inter-system direct data forwarding | CATT, China Telecom, Nokia, Nokia Shanghai Bell,ZTE |
| R3-203698 | Support of inter-node handover with a shared split (S)gNB | CATT, China Telecom, Nokia, Nokia Shanghai Bell,ZTE |
| R3-203699 | Futher clarification on support of inter-system direct data forwarding for CP/UP separation scenario | CATT, Nokia, Nokia Shanghai Bell,China Telecom,ZTE |
| R3-203783 | Correction of User Plane Inter-System Direct Forwarding | Nokia, Nokia Shanghai Bell |
| R3-203947 | Response to R3-203699 | Ericsson |
| R3-204273 | CB: # 85bis_InterSysDataFwd_E1_aspects - Summary of offline discussion | CATT - moderator |
| R3-204274 | Correction of User Plane Inter-System Direct Forwarding | Nokia, Nokia Shanghai Bell |
| R3-204275 | CB: # 86bis_UP-interSys_direct_Fwding_Correction - Summary of offline discussion | Nokia - moderator |
| R3-204276 | CB: # 87_5G_intraSysDirectFwd_Shared_SourceLS - Summary of offline discussion | ZTE |
| R3-204354 | CB: # 85bis_InterSysDataFwd_E1_aspects - Summary of offline discussion | CATT - moderator |
| R3-204373 | [Draft] LS about 5G Intra-system Various HO Scenarios Involving MR-DC | ZTE |
| 31.3.4.1 | Other Rel-16 Corrections | |
| R3-203242 | TS37.340 Stage2 Refined Descriptions of SCG Suspend&Resume Operation | ZTE |
| R3-203243 | TS36.423 Corrections of SCG Suspend&Release Behaviors with EN-DC in Rel-16 | ZTE |
| R3-203247 | Discussion on One PDU session with Multiple CU-UPs | ZTE Corporation |
| R3-203248 | Support one PDU session with multiple CU-UPs for TS38.401 | ZTE Corporation |
| R3-203249 | Support one PDU session with multiple CU-UPs for TS38.413 | ZTE Corporation |
| R3-203288 | On the challenges of TNL address discovery with the flexible NG-RAN Node ID length | Ericsson, Verizon |
| R3-203289 | Draft LS on broadcasting gNB ID length in system information block | Ericsson, Verizon |
| R3-203309 | Draft LS on Test Procedures for PWS | Ericsson, One2many |
| R3-203315 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-203316 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-203317 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-203335 | Full slot format support | Qualcomm Incorporated |
| R3-203336 | Full slot formats support in Intended TDD UL-DL Configuration | Qualcomm Incorporated |
| R3-203355 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Incorporated |
| R3-203359 | Corrections of procedures for PWS tests | Ericsson, One2many |
| R3-203426 | Correction to node name format | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-203560 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203561 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-203632 | SRS-RSRP configuration for CLI | Nokia, Nokia Shanghai Bell, China Telecom, Orange, LGE, ZTE |
| R3-203637 | Correction to SCG Resuming from suspension | Google Inc. |
| R3-203649 | Correction of last PDU session release | Huawei |
| R3-203719 | Completion of RAN UE ID | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-203720 | RAN UE ID for X2 | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-203721 | RAN UE ID for Xn | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-203722 | RAN UE ID for NG | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-203752 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-203753 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-203754 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-203755 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-203756 | On X2 support for UE CLI measurement for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-203757 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-203761 | gNB-CU-UP ID | Ericsson |
| R3-203784 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-203785 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-203802 | SRS-RSRP configuration for CLI | LGE, China Telecom, Orange, Nokia, Nokia Shanghai Bell, ZTE |
| R3-203836 | UL Data Split | Nokia, Nokia Shanghai Bell |
| R3-203861 | Correction on CLI | ZTE, Ericsson, LGE |
| R3-203862 | SRS-RSRP configuration for CLI | ZTE, Nokia, Nokia Shanghai Bell, CMCC, LGE, China Telecom, Orange, China Unicom |
| R3-203922 | Introduction of needForGapsInfoNR | Google Inc. |
| R3-204085 | RAN UE ID for NG | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-204086 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-204172 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204255 | Response LS on the LS For Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | ZTE |
| R3-204266 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204267 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204269 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204270 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204277 | CB: # 88_CLI - Summary of offline discussion | ZTE - moderator |
| R3-204278 | Full slot formats support in Intended TDD UL-DL Configuration | Qualcomm Incorporated |
| R3-204279 | CB: # 89_Full_slot_format_support - Summary of offline discussion | Qualcomm - moderator |
| R3-204280 | CB: # 90_S-NSSAI_range_correction | Nokia - moderator |
| R3-204281 | CB: # 91_Node_name_type - Summary of offline discussion | Ericsson - moderator |
| R3-204282 | CB: # 92_RAN_UE_ID - Summary of offline discussion | Ericsson - moderator |
| R3-204341 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-204342 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-204343 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung, China Telecom |
| R3-204352 | Response LS on the LS For Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | ZTE |
| R3-204355 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204364 | CB: # 90_S-NSSAI_range_correction | Nokia - moderator |
| R3-204365 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204366 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204367 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204368 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204369 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204370 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange |
| R3-204371 | CB: # 90_S-NSSAI_range_correction | Nokia - moderator |
| R3-204394 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange, Ericsson |
| R3-204395 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange, Ericsson |
| R3-204396 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange, Ericsson |
| R3-204397 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile, Huawei, CMCC, Deutsche Telekom, Interdigital, ZTE, Orange, Ericsson |
| R3-204398 | Slot length correction in Intended TDD UL-DL Configuration | Qualcomm Incorporated |
| R3-204399 | Response LS on the LS For Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | ZTE |
| 31.3.4.2 | Other TEI16 | |
| R3-203290 | Addition of Local NG-RAN Node Identifier. | Ericsson |
| R3-203291 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson |
| R3-203333 | Direct data forwarding from source node to target SgNB in NR SA to EN-DC inter-system handover | Qualcomm Incorporated |
| R3-203334 | Voice fallback triggered by PDU session resource setup | Qualcomm Incorporated |
| R3-203477 | SCTP association change when current SCTP association is failed | Nokia, Nokia Shanghai Bell, China Telecom |
| 31.4 | Rapporteur Corrections for Rel-16 | |
| R3-203166 | Rapporteur's Update for 38.424 | InterDigital |
| R3-203244 | Rapporteur Clean-ups of TS38.414 | ZTE |
| R3-203427 | Tabular and ASN.1 correction of messages of the EN-DC X2 Setup and EN-DC Configuration Update procedures | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-203428 | Tabular and ASN.1 correction of messages of the EN-DC X2 Setup and EN-DC Configuration Update procedures | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-203594 | Rapporteur Corrections to 38.401 | NEC |
| R3-203858 | Miscellaneous corrections to 37.473 | Huawei, China Unicom, Orange, TIM |
| R3-203859 | Miscellaneous corrections to 37.470 | Huawei, China Unicom, Orange, TIM |
| R3-204022 | CB: # 13_Rel-16_RappCorr - Summary of email discussion | InterDigital |
| R3-204025 | Rapporteur's Correction to XnAP version 16.1.0 | Ericsson |
| R3-204026 | Rapporteur's Correction to X2AP version 16.1.0 | Ericsson |
| R3-204073 | Rapporteur Clean-ups of TS38.414 | ZTE |
| 32 | Any other business | |
| R3-204061 | (reserved) | ETSI MCC |